Brand Guidelines

✅ Widgets on the PDP(product details pages), cart page and checkout page are shown with the right labeling in Arabic and English
✅ Widgets show Tamara's popup/page with the right content once tapped
✅ Widget behavior is correct on both desktop and mobile web
✅ Widget behavior is correct on Mobile apps (if applicable)
✅ Branding guidelines and assets (for logo at checkout page, footer icon, customisation) are as shared here:

Tamara Brand Guidelines

Payment options

✅ Tamara as a payment option, is shown based on the min/max configurations 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.)

✅ Users can trigger checkout and complete it successfully
✅ Checkout language (English/Arabic) matches the store interface
✅ Checkout details match the order at the store
✅ Order status matches the expected status on order completion (Authorised)
✅ If the order is not Authorised within 72 hours from when it is Approved, Tamara marks it as Expired.
✅ 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)
✅ ID verification flow should be working on all platforms, such as Web, Mobile Web, Mobile apps:
- ✅ If KSA setup is enabled, need to ensure that Nafath ID verification flow is working fine.
  - (a)To test, please follow the instructions here: For 🇸🇦 KSA Nafath ID verification process
- ✅ If UAE setup is enabled, need to ensure that Uqudo ID verification flow is working fine.
  - (a) To implement, please review the documentation here: UAE ID Verification via Uqudo
  - (b) To test, please follow the instructions here: For 🇦🇪 UAE Uqudo ID verification process

✅ 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 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

✅ Relevant merchant stakeholders should subscribe to https://status.tamara.co/ to get notifications regarding any planned maintenance activities, system updates or incidents.

✅ For merchants using SSL certificate pinning to connect with Tamara system - a security measure that ensures connections are only made to trusted servers like Tamara - Integration Manager or Account Manager to provide the latest certificate, on requirement.

*To be covered if you support such cases in your store's flow