Tabby

Tabby

This connector uses the Tabby API (buy now, pay later in the UAE, Saudi Arabia and Kuwait) of your merchant account: payments with their captures and refunds, checkout sessions, disputes and webhooks. Capture, refund and close are included but installed switched off.

Setup (2 minutes)

1. Sign in to the Tabby Merchant Dashboard (merchant.tabby.ai for the UAE, merchant.tabby.sa for Saudi Arabia) or ask your Tabby partner manager for the API keys.
2. Copy the secret key into TABBY_SECRET_KEY: sk_test_... for test payments, sk_... for live ones. The public key (pk_...) does not work here.
3. TABBY_API_URL is the API of your merchant region: https://api.tabby.ai for the UAE (and Kuwait), https://api.tabby.sa for Saudi Arabia. Tabby asks every call to go to the merchant region; a wrong region answers 403 or 404.
4. Install and run tabby_search_payments to check the key.

Identifiers: a payment id is a UUID assigned by Tabby. Your own order number is order.reference_id of the payment. To find a payment from an order number, list payments for the order date with tabby_search_payments (created_from / created_to) and match order.reference_id.

Workflow

• Recent payments: tabby_search_payments (20 per call, page with offset; without status only AUTHORIZED and CLOSED payments). Then tabby_get_payment_details for the full record.
• Status meaning: AUTHORIZED = customer approved, not yet captured; CLOSED = captured (fully) or closed; REJECTED and EXPIRED = no money moved. Captures and refunds are listed inside the payment.
• A checkout that did not finish: tabby_get_checkout_session.
• Disputes: tabby_list_disputes, then tabby_get_dispute; days_left is the time before the dispute is approved automatically.
• Webhooks: tabby_list_webhooks with your merchant code.

Writes switched off: tabby_create_capture (captures money of an AUTHORIZED payment), tabby_create_refund (refunds a CLOSED payment, instantly) and tabby_close_payment (releases what is not captured). An admin turns them on deliberately. Before each call show the user the payment, the amount and the currency and wait for a yes. Pass a reference_id so a retry is not executed twice.

Amounts: strings with up to 2 decimals (AED, SAR) or 3 (KWD). Dates and times are UTC, ISO 8601.

Errors: 401 means a wrong secret key or a public key; 400 with an empty body can also be a missing key at the edge. 403 or 404 for a payment that exists usually means the wrong region in TABBY_API_URL. 409 on a refund means the payment is not refundable yet (not CLOSED) or the amount is too high.

Limitations: creating checkout sessions, updating payments, registering webhooks and answering disputes are not part of this connector; do those in the Merchant Dashboard.