Tamara for business: merchant payments, fees & integrations
Explore Tamara merchant onboarding, Shopify and WooCommerce setup, settlement reporting and refunds, with clear checks for eligibility and commercial terms.
Faisal Karkoh · 10 Oct 2026 · 6 min read
A customer orders two products, one ships today and the other is cancelled because stock was wrong. That ordinary retail problem is a useful test of an installment-payment integration. Can the store update the payment correctly, explain the revised balance and match the eventual settlement?
Shortlist Tamara only after merchant eligibility, commercial terms and the store’s cancellation/refund route are confirmed. Defer rollout if staff cannot reliably adjust a partly fulfilled order or reconcile its settlement. That is the decision this guide works through: checkout approval is the beginning, and a correct retained balance after returns is the useful acceptance test.
Confirm the merchant market before choosing an integration
Tamara's developer introduction names Saudi Arabia, the UAE and Bahrain. Its marketing site also offers a Kuwait country selection, but a country selector does not establish current new-merchant eligibility. Obtain explicit confirmation for the legal entity and activity.
A consumer being able to use a product in a market does not automatically establish that a new merchant can onboard there. Ask the onboarding team which channels and payment options the proposed account will be enabled for, what business evidence it needs and which payout account it accepts.
Keep that confirmation with the implementation brief. If the business has entities in two countries, do not assume one merchant account, contract or integration configuration covers both.
Follow the order from checkout to completion
Keep a simple exception record during that test: original order reference and amount, item being removed, amount already captured, action requested, provider response and remaining balance. If the response is uncertain, stop and check status rather than issue a second financial action. The completed record should explain both the customer balance and the finance entry. This proposed worksheet is deliberately independent of the dashboard so support and finance can audit the same case.
Tamara's online checkout documentation describes an order lifecycle involving authorization, capture, cancellation and refunds. The important implementation question is which store action maps to each provider action for your selected integration.
Authorization is not a synonym for a completed payout. Nor should a customer's return to the success page be the only evidence used to release stock. Ask the implementation team to document the authoritative provider status and how it reaches the store.
| Business event | What the team must establish | Launch gate |
|---|
| Customer completes checkout | Store and provider reference the same approved order and amount. | Accept only when the provider status, store status and amount can be matched without relying on the success page alone. |
| Order is ready to fulfill | The required authorization/capture behavior follows the current integration contract. | Accept only when the team has documented which provider state permits fulfillment. |
| Unshipped item is cancelled | The correct cancellation or adjustment route is used for the payment state. | Rework before launch if staff cannot tell when to cancel, adjust or refund. |
| Delivered item is returned | The refund is recorded against the original provider order. | Accept only when support and finance can see the original order reference and remaining amount. |
| Settlement arrives | Orders, fees and adjustments explain the bank deposit. | Rework before launch if finance cannot tie the net deposit to the report. |
These are acceptance criteria, not replacement API instructions. Exact event names, timing and permitted amounts should come from the current documentation and the merchant's enabled configuration.
Choose the supported platform route
Use the platform quick start to find the current integration. Tamara publishes separate instructions for its Shopify payment app and WooCommerce configuration.
On Shopify, distinguish the payment app from any storefront messaging component. Displaying an installment estimate on a product page does not prove checkout is enabled. Test how the final total changes with shipping, discounts and relevant tax. The Shopify installation guide explicitly says its app does not support the “Enable test mode” checkbox. Agree a supported validation route with Tamara rather than treating a generic Shopify test toggle as a sandbox.
On WooCommerce, use a staging copy with representative products and record the plugin version. Test a successful order, an abandoned checkout and a retry after a failed attempt. Confirm how the integration updates order status and where staff can find the provider reference.
A custom checkout needs an explicit exception path. If a webhook/update is missed or a network problem interrupts the redirect, follow Tamara's order-status check approach: recheck Tamara order status and avoid repeating a financial action blindly. The Tap guide discusses similar payment-state responsibilities for a conventional gateway.
Work through a partial-order example
Imagine an order containing a lamp for AED 300 and a side table for AED 700. Shipping is free and this simplified example ignores tax. The customer completes a checkout for AED 1,000; the table then becomes unavailable.
Before taking an action, staff check the provider order state. If the payment has not reached the relevant captured state, the appropriate route may be a cancellation or adjustment. If AED 1,000 has already been captured, the team needs the supported partial-refund route for AED 700. Do not choose the operation from the storefront status label alone.
After the action, verify the provider's remaining amount, the store order, the customer notification and the accounting record. The expected retained sale in this simplified example is AED 300 before fees. If the integration cannot support the required partial-order workflow, establish a documented alternative before rollout.
Run this scenario through the validation route supported by the selected integration and confirm how it maps to the actual merchant configuration. This article does not claim the example was executed on a live Tamara account.
Budget from the contract and reconcile from the report
Do not copy an unofficial merchant-fee percentage into a business case. Obtain the commission, fixed charges, tax treatment, refund-fee policy and any other deductions in writing for the correct country. The published Bahrain merchant terms illustrate why country and agreement matter; they are not a universal GCC quote.
Tamara's settlement guide describes fixed and flexible models. It states that fixed settlement reports are issued every Sunday and processed every working Tuesday, with a 25 SAR/AED fee if the settlement amount is less than 2,500 SAR/AED; for the default flexible model, Tuesday processing applies only when the account reaches or exceeds the 2,500 SAR/AED threshold. The same page also says settlements are issued on Saturday and bank transfer is Tuesday, so confirm the current schedule and any country/account-specific terms rather than treating those figures as a universal quote. The settlement dashboard guidance identifies the account's expected payment date, cycle and model. Use those account details and the agreement to establish the actual schedule.
For every deposit, retain the report that links original orders, adjustments, refunds and fees to the net amount. Assign an owner to unexplained differences. A successful checkout test is incomplete until finance can explain a settlement containing a prior-period refund.
Use the pilot to expose exceptions
Choose products with known margins and manageable returns. Review approval rate, completed orders, net contribution, cancellations and staff time. Include at least one partial return and one failed or retried checkout in the test plan rather than waiting for a customer to discover the problem.
Compare Tabby only on equivalent eligibility, contract terms and product assumptions. If platform behavior is the constraint, return to the platform comparison before adding more payment options. Tamara is a stronger fit when checkout and after-sales operations both work predictably; a prominent badge cannot compensate for an unresolved refund process.
Information checked: 9 October 2026. Official sources are linked beside the relevant claims.