Tabby

Tabby: Merchant Overview Of Flexible Payments Across Online And In-Store Checkout

Tabby is a buy now, pay later payment method that merchants can add to online checkout and in-person sales flows. It is designed to let shoppers split purchases into multiple payments, while merchants receive the full amount (minus applicable fees) according to a payout schedule. Tabby supports selling online, in-store through existing POS setups, and remote selling through payment links.

Tabby Overview For Merchants

Tabby positions its merchant offering around flexible payment plans that can be used across common commerce touchpoints:

• Online checkout: shoppers can pay in 4 interest-free instalments or spread payments over up to 12 months.

• In-person acceptance: merchants can accept Tabby through an existing POS or let customers tap their Tabby Card.

• Payment links: merchants can get paid by sharing a payment link with customers.

Tabby also highlights commercial outcomes for merchants, including reported increases in basket size and conversion, and a larger spend per customer, tied to the availability of instalment plans.

Where Tabby Fits In Your Payments Stack

From a merchant implementation perspective, the provider functions as an additional payment option that can sit alongside card payments and other alternative payment methods. Depending on your setup, Tabby can be enabled via:

• App plugins for commerce platforms

• Low-code and no-code options

• Custom API-based integration for more control over checkout and post-payment operations

The objective is to let customers choose a Tabby plan at checkout, while merchants manage payouts, disputes, refunds, and reporting through merchant tools.

Payment Plans And Customer Experience

Pay In Installments

Tabby’s instalment proposition includes:

• Pay in 4 interest-free instalments

• Longer instalment options up to 12 months (plan availability can depend on the basket and eligibility)

These options can be presented at checkout for online purchases and used in-store through Tabby Card, paylinks, or QR-based flows.

Pay Next Month

Tabby also documents a “pay next month” option, designed for categories such as groceries, food, and rides, where the customer pays at the end of the month.

Payment Acceptance Channels

Online (Web)

For web stores, Tabby can be offered as a checkout payment method, including via platform plugins and custom integrations. The customer flow includes a hosted checkout experience where payment is created and authorized.

In-Store (POS Context)

For in-store sales, Tabby can be accepted through an existing POS setup, including a customer tapping with Tabby Card. The documentation also describes offline integration approaches, including paylinks and QR-based fallback.

Remote Selling With Payment Links

Tabby supports sending payment links to customers. This can be used for assisted sales, phone-based orders, or situations where the customer completes the payment on their own device after receiving a link (for example, via SMS or push).

Supported Markets And Currencies

The documentation and merchant materials focus on the GCC operating markets, including:

• Saudi Arabia (KSA)

• United Arab Emirates (UAE)

• Kuwait

Currency support is aligned with these markets:

• SAR

• AED

• KWD

For platform use cases, the documentation describes multi-currency processing and currency conversion behavior. For example, a store can have a different base currency while Tabby checkout and merchant settlement are processed in the customer’s billing currency, with currency conversion applied where relevant.

Payouts And Settlement Cadence

How merchants receive funds:

• Merchants receive payouts to a business bank account via bank transfer.

• Payout timing follows a merchant-selected payout cycle, with options that include fixed weekly payouts and a flexible cycle.

• Tabby provides payout reporting, including order details, fees deducted, net transferred amounts, and refund adjustments.

Tabby also documents a weekly payout day (working Monday) under payout cycle descriptions.

Merchant Tools: Reporting, Dashboard, And Operations

Merchant-facing tools and reporting include:

• Merchant Dashboard and Tabby Business app for accessing payouts and managing the account.

• Payout reports with a transaction-level financial summary (sales, refunds, fees/commissions, total payout).

• Operational visibility to support reconciliation and day-to-day settlement tracking.

Disputes, Chargebacks, And Risk Operations

Dispute management exist in two ways:

• A merchant-facing disputes workflow described in help materials for accessing disputes and understanding dispute statuses.

• A Disputes API that is designed to simplify dispute handling, including retrieving disputes, viewing details, approving or challenging disputes, and uploading attachments.

Developer And Integration Options

Tabby provides multiple integration approaches for merchants, including platform plugins and a public API documentation set.

Platform Plugins And Supported Ecommerce Platforms

The documentation includes platform-specific implementation guidance for:

• Shopify

• Salla

• Zid

• WooCommerce

• Magento 2

• OpenCart

• Matjrah

• Salesforce

• ExpandCart

Hosted Checkout And API-Based Integration

API documentation describes a flow that includes:

• Checkout process for customer data collection and authorization

• Payments operations that cover capture, refund, close, and retrieval

• Webhooks for payment status updates and verification flows

• Disputes endpoints for dispute operations

The documentation describes both test and live usage within a single environment, with test and live keys.

Webhooks

Webhooks are a mechanism to ensure a seamless payment verification flow. API references include endpoints to register, retrieve, update, and remove webhooks.

Mobile SDKs

Tabby documentation includes Mobile SDKs and references mobile integration options, supporting in-app experiences and mobile commerce implementations.

Conclusion

Tabby is a BNPL payment method designed for merchants that want to offer instalment-based checkout across online and in-store commerce, with additional support for payment links and offline flows. Its documentation emphasizes merchant enablement through plugins and custom APIs, transaction-based pricing calculated by merchant profile, weekly payout options via bank transfer, and operational tooling for reporting, disputes, and payment status verification via webhooks. For merchants operating in Saudi Arabia, the UAE, and Kuwait, Tabby’s documented currency support (SAR, AED, KWD) and platform integrations provide a clear framework for adding flexible payments to standard checkout and POS experiences.