Go-Live Testing Checklist
This is an elaborated list of needed checks to validate an integration completion. Checks marked with ( * ) are optional depending on the merchant support for that use case.
Brand Guidelines
- β The widget is shown with the right labeling in Arabic and English
- β The widget shows Tamara's popup/page with the right content once tapped
- β The widget behavior is correct on both mobile and web (desktop and mWeb)
- β The widget behavior is correct on mobile apps (if applicable)
- β The assets (for logo at checkout page, footer icon, customisation) are as shared here: https://drive.google.com/drive/folders/1_lSGwnwAwudSsGXDBH4k_dliuqIliVdO
Payment options
- β
Tamara as a payment option, is shown based on the min/max configurations (API for eligibility check) set for the merchant account
- β less than min*
- β more than max
- β within range
- β Tamara as a payment option, is shown with the right labels, wherever applicable
- β Tamara's icon is shown next to the options
- β Tamara's icon is present wherever payment options are listed (footer, cart page, etc.)
Checkout
- β Users can trigger checkout and complete it successfully
- β Checkout language matches the store interface
- β Checkout details match the order at the store
- β Order status matches the expected status on order completion (Authorised)
- β Order payload is passed correctly (order reference id, items' details, totals, and consumer details)
- β
Customer is re-directed correctly in all scenarios
- β Success
- β Cancelation
- β Failure
- β Checkout is checked on Mobile Web
- β Checkout is checked on Mobile apps (if applicable)
Post-Order
- β Communication with customer mentions Tamara as the payment method
- β Customers receive order updates on shipping (from the merchant, if Tamara capture notifications are off)
Order Management
- β Order authorisation happens automatically after order approval without any issue
- β Order updates are triggered correctly from the dashboard or merchant OMS, if integrated, and reflect correctly at Tamara
- β Order status at merchant end and Tamara end are synced/matched
- β Check for order status - Pull Mechanism
- β
Cancellation flow (a cancel API call is triggered to Tamara on cancelation happening from different initiation points)
- β Full cancellation
- β Partial cancellation*
- β
Capture flow ( a capture API call is triggered to Tamara on shipping the order )
- β Full capture
- β Partial capture*
- β
Refunds flow (a refund API call is triggered to Tamara on refund happening from different initiation points)
- β Full refund
- β Partial refund*
- β All Tamara orders refunds are handled over Tamara ONLY; refund to store wallet, etc., is NOT allowed.
- β Webhook(s) correctly configured
Status Page
- β Relevant merchant stakeholders have subscribed to https://status.tamara.co/ to get notifications about updates or incidents.
*To be covered if you support such cases in your store's flow
Updated 5 months ago