Linkit
Plugins

Tabby BNPL

Install and configure Tabby Buy Now Pay Later integration for KSA, UAE, and Kuwait.

Tabby BNPL Integration

Tabby is the leading Buy Now, Pay Later (BNPL) platform in Saudi Arabia, UAE, and Kuwait. The Linkit Tabby integration provides 7 apps covering the full BNPL lifecycle — from checkout session creation to dispute management.

Tabby is regulated by SAMA (Saudi Arabian Monetary Authority) and supports SAR, AED, and KWD currencies.

Prerequisites

  • A Tabby merchant account (merchant.tabby.sa for KSA)
  • merchant_code and secret_key from Tabby onboarding
  • Linkit organization with at least one connected platform (Salla, Zid, HungerStation, etc.)

Available Apps

AppTypePurpose
Tabby CheckoutPaymentsCreate BNPL checkout sessions with customer eligibility scoring
Tabby PaymentsPaymentsCapture, refund, and close payment lifecycle management
Tabby Webhook BridgeAutomationRegister and receive Tabby payment status webhooks
Tabby DisputesPaymentsList, challenge, and submit evidence for payment disputes
Tabby BNPL AnalyticsAnalyticsBNPL adoption rates, approval rates, and conversion tracking
Tabby POS Payment LinksPOSIn-store QR code payment links for POS transactions
Tabby ReconciliationAutomationCron-based payment status sync and missed webhook recovery

Installation

  1. Navigate to App Store in the Linkit dashboard
  2. Search for Tabby in the Payments or POS categories
  3. Install the desired apps (all are independent — install only what you need)
  4. Enter your Tabby credentials in the app configuration modal:
    • Merchant Code — from Tabby merchant portal
    • Secret Key — API secret key for authentication
    • Base URLhttps://api.tabby.sa (KSA) or https://api.tabby.ai (UAE/Kuwait)

Configuration

Each installed Tabby app reads credentials from the organization app's custom params:

ParameterDescriptionDefault
merchant_codeYour Tabby merchant code
tabby_secret_keyAPI secret key (or use the API Secret field)
tabby_base_urlAPI endpointhttps://api.tabby.sa
auto_captureAuto-capture authorized paymentsfalse
default_currencyDefault currency for sessionsSAR
default_langCheckout languagear
webhook_auth_tokenCustom auth token for webhook verification

POS Integration

Tabby POS payment links are managed via the Unified Providers Paylinks API with "provider": "tabby":

POST   /api/v1/providers/paylinks              — Create payment link
GET    /api/v1/providers/paylinks              — List payment links
GET    /api/v1/providers/paylinks/{id}          — Check status
POST   /api/v1/providers/paylinks/{id}/capture  — Capture payment
POST   /api/v1/providers/paylinks/{id}/cancel   — Cancel link

Flow

  1. Cashier creates an order → calls POST /api/v1/providers/paylinks with "provider": "tabby"
  2. QR code URL is returned → display to customer
  3. Customer scans QR → completes Tabby checkout on their phone
  4. Tabby webhook confirms authorization → auto-capture if enabled
  5. Cashier confirms → order marked as paid

See the Providers Paylinks API Reference for full endpoint documentation.

Webhooks

The Tabby Webhook Bridge app registers a webhook URL with Tabby and handles incoming events:

  • authorized — Customer completed checkout, ready for capture
  • closed — Payment fully captured and settled
  • expired — Session timed out without completion
  • rejected — Customer not eligible for BNPL

Tabby sends webhooks from specific IP addresses. Ensure your firewall allows: 34.166.36.90, 34.166.35.211, 34.166.34.222, 34.166.37.207, 34.93.76.191, 34.166.128.182, 34.166.170.3, 34.166.249.7

Data Collections

CollectionPurpose
tabby_webhooksRaw webhook audit trail for all incoming Tabby events
tabby_paylinksPOS payment link records with session/payment tracking

Regional Endpoints

RegionAPICheckoutMerchant Portal
Saudi Arabiaapi.tabby.sacheckout.tabby.samerchant.tabby.sa
UAE / Kuwaitapi.tabby.aicheckout.tabby.aimerchant.tabby.ai

Testing

Tabby provides testing credentials and a Postman collection:

Set is_test: true in your webhook registration to receive test events only.