Versions Compared

Old Version 17

changes.mady.by.user Benet, Anton

Saved on

compared with

New Version 18

changes.mady.by.user Fagundes, Silvia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Categories

Outcome

Work Required

How to test

Owner

1

System Architecture

  • Transactional emails are moved from Braze to AWS SES

  • Switch to AWS SES to send transactional emails

  • Create email input field in Sanity

  • Set up email subdomain structure

  • Transactional emails have the same content

  • Emails are sent from SES instead of Braze. This can confirmed by looking at the email subdomain

Haris

2

Authentication and Authorization

  • Guest authentication is enabled

  • Loyalty accounts are decoupled from guest users

  • Develop a Guest Auth token since guests don't have accounts in Cognito or User DB

  • Remove loyalty account check for guest checkout users

  • Verify token generation and validation for guest users

  • No error is triggered due to missing loyalty account

Magdalena

3

Data Security and Compliance

  • Secure and compliant data storage

  • Guest Token actions are limited and controlled

  • Implement configurable time period for storing Guest Order data

  • Add security measures to limit guest actions, implement a guard to restrict Guest Token usage

  • Decide and implement logic for Guest Token removal

  • Guest order data is removed after set period

  • Allowed actions can be performed with Guest token - e.g. priceOrder, validateCommitOrder, commitOrder, getOrder, etc

  • Unauthorized actions can’t be performed with Guest token

Magdalena

4

User Experience and Interface

  • Complete frontend flows for guests users

  • Implement event tracking

  • Remove 'Save Card' option at Payment step

  • Add modal to allow users to ‘Continue as a guest’

  • Adjust data displayed in the order confirmation page

  • Add new events and assure data flow to mParticle and Amplitude

  • Guest users can’t save card

  • Guest user is able to add email in modal and place order for all service modes

  • Confirmation page display correct information

Magdalena

5

Legal

  • Required legal disclaimers for guest checkout are in place

  • Create a static page with guest checkout terms and conditions

n/a

Melina

Detailed Break-down

Scope/ Outcome

Work Required

Available on staging

Status

  • Add configurable time period of storing the Guest Order data in the database. Configure to 10 year for DE

  • Preventing the guest user from seeing app content dedicated for registered users only

  • Add a security layer limiting actions allowed for the orders with Guest token. Actions allowed for example: priceOrder, validateCommitOrder, commitOrder, getOrder, etc

  • Add a guard that allows to use of the Guest Token only for the allowed actions

  • Creating Guest Token- To place an order as a Guest users require to have be authenticated on our platform/ In order to do that we need to create a Guest Auth token. We can’t follow the current path for collecting it because Guests don’t have accounts in Cognito and in the User DB entries.

  • Save Card Option Removed at the Payment step

    Image Modified

  • Added Modal to continue as a guest

    Image Modified

  • Adjusted data on the confirmation page

  • QA Testing

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-908
F

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-949
F

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-959
F

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-941
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-947
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-957
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-956
M

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-912
W
Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1010
W

Status
colourBlue
titleWork in Progress

  • Accommodate new transactional email communication with AWS SES instead of Braze

  • Decide and execute when guest token should be removed, so no other order can be made with that token to guarantee anonymity

  • Prevent error appearing on the success page due to loyalty account request which does not exist for guest users

  • QA Testing

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1006

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-909

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-962

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1006

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-909

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-962

Status
titleTo do

  • Create a new static page for guest terms and conditions and link it in the flow

  • Change copy to “choose payment' instead of “add payment” at the /cart/payment page

    Image Modified

  • Implement tracking events to flow to Amplitude

  • E2E QA Testing

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-948

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1015

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1003

Status
titleTo do


(info) Further Improvements to Guest Checkout not in scope for MVP

Future Enhancements

Context

Ability to handle guest checkout orders in the direct tool

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-910

  • Melina clarified that refunds are managed directly via VR Payment’s dashboard so there’s no need to handle guest checkout orders in the Support Tool

  • Orders are identified in VR Payment’s dashboard using the order time, store ID and order value

Allows guests users to create account after placing order

  • After enabling loyalty, we could offer guests to create an account by displaying the points that could have been earned.

Allow guests users to opt in for email marketing communications

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1008

  • Allowing guests to opt in for marketing communications would allow us to increase our contactable user base

  • However, this requires checking with legal to ensure compliance with GDPR and local regulations

Image RemovedImage Added

Allow operators to enable/disable guest checkout directly in Sanity and manage other related configurations

Jira Legacy
serverSystem JIRA
serverId255417eb-03fa-3e2f-a6ba-05d325fec50d
keyTRX-1009

  • Initially the feature will be controlled via Launch Darkly to perform A/B testing

  • Once the feature is stable, we will look at moving the configuration into Sanity

Image RemovedImage Added

(question) Open Questions

...