Skip to main content

Tabby & Tamara (BNPL)

Tabby and Tamara are buy-now-pay-later providers popular in Saudi Arabia and the UAE. The shopper splits the purchase into instalments; you are paid in full by the provider.

These integrations are incomplete — do not enable them on a live store

TakeTheme can create a Tabby or Tamara checkout session and send the shopper to it, but there is no callback handler for either provider. When the shopper finishes paying, nothing tells TakeTheme.

Because online payments use deferred order creation, that means:

  • No order is created, even though the customer has been charged.
  • The payment record stays Unpaid.
  • The customer sees a success page with no order behind it.

Every completed BNPL payment would have to be found in the provider's dashboard and re-created by hand. Leave both methods deactivated until callback handling ships.

The rest of this page documents what exists, so the configuration is ready when the integration is completed.


Tabby

Settings → Payments → Tabby.

CredentialRequired
Secret KeyYes
Publishable KeyYes
Merchant CodeYes
Webhook Secret

TakeTheme creates a Tabby session for the order total (items + shipping + tax) and redirects the shopper to the instalments product. If Tabby rejects the shopper — its risk engine declines a share of orders by design — the checkout fails and they must choose another method.

Tamara

Settings → Payments → Tamara.

CredentialRequired
API TokenYes
Notification Token
Public Key
SettingDefault
Environmentsandbox

Tamara's sandbox and production environments use different API hosts and different tokens — they are not interchangeable.


Known limitations

Beyond the missing callback:

  • The order is sent as a single line item ("Order Payment") rather than the real basket. BNPL providers use item detail for risk scoring and dispute handling.
  • A placeholder buyer email is sent instead of the shopper's real address.
  • Tamara defaults the buyer country to SA, regardless of the shipping address.