chore: email templates updated

[gitanjli525]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

• Updated the HTML templates to new designs in backend

• Look at the below screenshots

• Old
  
  
  

• New
  
  
  
  
  
  
  
  
  
  
  

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

• Currently used email templates were following Juspay old email structure, modified them to the new updated designs

How did you test it?

• Tested using AWS SES email service & Postdrop, attached the screenshots

Please find below curls for same :

curl --location 'http://localhost:8080/user/connect_account'
--header 'Content-Type: application/json'
--data-raw '{
"email": "gitanjli524@gmail.com"
}'

curl --location 'http://localhost:8080/user/user/invite_multiple?is_token_only=true'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiNGMyMjUyMTktZGVjNC00M2VlLTgyOTktMTBjMDRmYzkxYWYzIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzA2ODY5OTYzIiwicm9sZV9pZCI6Im9yZ19hZG1pbiIsImV4cCI6MTcxNjk4MTMwNSwib3JnX2lkIjoib3JnX2dMbEJuQzgwVTgxNzlVTnozdm5sIn0.JsZr4aSFm_2C8si9byvS02kIAaYvpNNF_xidZSRm1sU'
--header 'Cookie: login_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiNGMyMjUyMTktZGVjNC00M2VlLTgyOTktMTBjMDRmYzkxYWYzIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzA2ODY5OTYzIiwicm9sZV9pZCI6Im9yZ19hZG1pbiIsImV4cCI6MTcxNjk4MTMwNSwib3JnX2lkIjoib3JnX2dMbEJuQzgwVTgxNzlVTnozdm5sIn0.JsZr4aSFm_2C8si9byvS02kIAaYvpNNF_xidZSRm1sU'
--data-raw '[
{
"email": "gitanjli524+098763@gmail.com",
"name": "25",
"role_id": "merchant_view_only"
}
]'

curl --location 'http://localhost:8080/user/forgot_password'
--header 'Content-Type: application/json'
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiZDM2NzMyMTUtYWU3NS00NGMzLWJiYzEtMGY3YmMxYmYwMjdmIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzEyMjE0NDE5Iiwicm9sZV9pZCI6Im9yZ19hZG1pbiIsImV4cCI6MTcxMjM4NzMyOSwib3JnX2lkIjoib3JnXzhLb2lWNmhrcG9KSGZNcllER1ZhIn0.H2G9oGp_JBoz3k5S7fMvaaJ9T0cG5VtUjM0hU3ltM3g'
--data-raw '{
"email": "gitanjli524@gmail.com"
}'

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[Riddhiagrawal001]

Why do we need this change ?

[gitanjli525]

To maintain the consistency, as in other emails, if you see, we use username for html files and user_name is what we are assigning to username. No other reason. Hence utilised "username" in the Magiclink.html file where it was required rather than user_name.

[PritishBudhiraja]

I don't think so head tag is required just check once it was previously working.

[ThisIsMani]

Sometimes we are using Hyperswitch and sometimes HyperSwitch. Can we make this consistent.

[ThisIsMani]

Suggested change

	Hi {username}, You have received this email because your
	Hi {username}, you have received this email because your

[ThisIsMani]

Suggested change

	Dear {username}, We are thrilled to welcome you into our
	Dear {username}, we are thrilled to welcome you into our

[ThisIsMani]

Suggested change

	This link provides instant access to hyperswitch
	This link provides instant access to Hyperswitch

[ThisIsMani]

Suggested change

	<li>Enter your login credentials to log in.</li>
	<li>Enter your login credentials.</li>

[ThisIsMani]

Create and link an issue.