Saudi merchants looking for how to integrate BNPL into ecommerce checkout in Saudi Arabia are usually asking one question: how do you add Tamara and Tabby correctly while remaining compliant with Saudi regulations? The answer is straightforward—integrate the providers through their official APIs, generate ZATCA-compliant invoices for every successful order, and build the checkout around Saudi payment behaviour rather than copying a Western e-commerce flow.

More than 42% of Saudi consumers have already used Buy Now Pay Later (BNPL) services, and the Saudi BNPL market is projected to reach approximately US$5.29 billion in 2026. A Saudi e-commerce checkout without Tamara or Tabby is no longer a complete Saudi checkout—it is missing one of the highest-converting payment methods available in the Kingdom.

For merchants building a custom platform, BNPL integration is no longer simply another payment gateway alongside mada or Apple Pay. It influences checkout conversion, average order value, customer trust, payment flexibility, and even how your ZATCA Phase 2 invoicing workflow operates.

At Logiolegion, we build Saudi-first custom commerce platforms that integrate BNPL providers, ZATCA e-invoicing, Saudi payment gateways, Arabic RTL interfaces, and enterprise commerce workflows into a single architecture instead of treating each integration as an isolated feature.

---

Why BNPL Is Non-Negotiable for Saudi E-Commerce Checkout in 2026

Saudi online shopping behaviour has changed dramatically over the last few years. Customers increasingly expect to split purchases into manageable monthly installments without paying interest, particularly for fashion, electronics, furniture, beauty, travel, healthcare, and premium lifestyle products.

Industry data consistently shows that BNPL can increase checkout conversion by 10–25% for purchases between SAR 200 and SAR 1,500. It also increases average order value by 30–80% because customers become comfortable purchasing higher-value products when payment is divided into smaller installments.

This behavioural shift is especially strong among younger Saudi consumers, who generally prefer interest-free installment options instead of traditional credit cards. Rather than delaying purchases, many shoppers actively look for the Tamara or Tabby logo before deciding where to complete their purchase.

Saudi Arabia's transition toward a cashless economy has accelerated this trend even further. Electronic payments now account for approximately 79% of all retail transactions, surpassing the Kingdom's original Vision 2030 target ahead of schedule. Digital-first payment behaviour has become the default rather than the exception.

For Saudi merchants, BNPL is no longer positioned as a premium checkout option. It sits alongside mada, Apple Pay, STC Pay, and credit cards as one of the standard payment methods expected by customers.

Unlike many international markets where dozens of BNPL providers compete simultaneously, Saudi Arabia revolves around two dominant players:

• Tamara
• Tabby

Both providers operate under the supervision of the Saudi Central Bank (SAMA) and have become the default BNPL options recognised by Saudi consumers.

Ignoring BNPL does not simply remove one payment option from your checkout.

It removes one of the highest-performing conversion tools available to Saudi e-commerce businesses.

---

Tamara vs Tabby — Which Saudi BNPL Provider Should You Integrate First?

One of the most common questions merchants ask is whether they should integrate Tamara or Tabby first.

For stores focused primarily on Saudi Arabia, the answer is generally straightforward.

Integrate Tamara first.

Tamara is Saudi-native, headquartered in Riyadh, holds a full SAMA consumer finance licence issued in 2025, and consistently demonstrates stronger approval rates for Saudi consumers than Tabby.

Tabby remains an excellent addition to a Saudi checkout, particularly for merchants serving multiple GCC markets. Following its headquarters relocation to Saudi Arabia in 2024 and the acquisition of Tweeq, Tabby has strengthened its Saudi market position considerably while continuing to maintain strong coverage across the UAE and neighbouring GCC countries.

The best-performing Saudi checkouts eventually integrate both providers.

However, if budget or implementation time only allows one initial integration, Tamara generally delivers better results for Saudi-first businesses.

Factor	Tamara	Tabby
Founded	Riyadh (Saudi-native)	Dubai (Headquarters relocated to Saudi Arabia in 2024)
SAMA licence	Full Consumer Finance Licence (2025)	SAMA-licensed BNPL provider
Saudi approval rate	Higher approval for Saudi customers	Lower than Tamara in Saudi, improving steadily
Sharia compliance	Interest-free with no fees for on-time payment	Similar Sharia-compliant structure
Payment splits	2-installment and 4-installment plans	2-installment and 4-installment plans
Merchant Discount Rate (MDR)	Typically 3–6%	Typically 3–6%
Merchant ecosystem	Strong Saudi retailer network	Strong GCC retailer network
Best first integration	Yes for Saudi-first businesses	Recommended as second provider for broader customer coverage

There is another important distinction between the Saudi and UAE markets.

In the UAE, many merchants report stronger approval rates from Tabby than Tamara.

Saudi Arabia demonstrates the opposite pattern.

Tamara generally approves a higher percentage of Saudi shoppers because its underwriting models have been built specifically around Saudi consumer behaviour, Saudi banking relationships, and Saudi financial history.

This difference can directly influence checkout conversion.

A higher approval rate means fewer declined applications, fewer abandoned carts, and more completed purchases.

Merchants operating exclusively inside Saudi Arabia should therefore consider Tamara their primary BNPL provider.

Tabby should then be added to increase approval coverage, provide customer choice, and support shoppers already familiar with the Tabby ecosystem.

Large enterprise retailers increasingly display both options, allowing customers to select their preferred BNPL provider while maximising approval opportunities across different consumer segments.

The objective is not choosing a winner.

The objective is ensuring that the largest possible percentage of Saudi shoppers can complete their purchase successfully using their preferred payment method.

How to Integrate Tamara into a Saudi E-Commerce Checkout

Step 1 — Tamara Merchant Account Setup (Saudi-Specific Prerequisites)

Before writing a single line of code, your business must complete Tamara's merchant onboarding process. Unlike a generic payment gateway, Tamara operates under the supervision of the Saudi Central Bank (SAMA), making merchant verification significantly more comprehensive.

To become a Tamara merchant in Saudi Arabia, businesses generally need:

• A valid Saudi Commercial Registration (CR)
• A Saudi VAT registration certificate
• A corporate Saudi bank account (such as SNB, Al Rajhi Bank, Riyad Bank, Banque Saudi Fransi, or SAB)
• National Address registration
• Business owner verification documents
• Website or mobile application ready for review

After the documentation review, Tamara provides sandbox credentials so development can begin while compliance checks continue.

Merchant verification includes full Know Your Business (KYB) procedures because Tamara now operates under a full SAMA consumer finance licence rather than simply functioning as a BNPL provider.

---

Step 2 — Tamara REST API Integration

Custom Saudi e-commerce platforms generally integrate directly with Tamara's REST APIs.

The primary checkout workflow looks like this:

Customer selects Tamara →

Merchant backend creates checkout session →

Tamara validates customer →

Customer completes approval →

Tamara redirects customer →

Merchant receives webhook →

Order confirmed →

ZATCA invoice generated.

The most important endpoint is:

POST /checkout

This endpoint creates a BNPL checkout session and returns the hosted checkout URL where the customer completes financing approval.

Typical request payload includes:

• Merchant reference ID
• Order total (SAR)
• Currency
• Consumer details
• Shipping information
• Billing information
• Complete line items
• Tax amounts
• Discount values
• Success URL
• Failure URL

Consumer information should always include:

• Full legal name
• Saudi mobile number (+966 format)
• Email
• Shipping address

Tamara performs identity verification during checkout using the supplied information.

---

Step 3 — Handle Tamara Webhooks Correctly

Creating the checkout session is only the beginning.

Your backend must continuously listen for webhook events that determine the final order state.

Typical webhook events include:

• order.approved
• order.declined
• order.expired
• order.cancelled
• order.refunded

Only order.approved should trigger:

• inventory deduction
• warehouse fulfilment
• shipping creation
• customer confirmation
• ERP updates
• ZATCA invoice generation

Many developers mistakenly fulfil the order immediately after redirecting customers to Tamara.

This creates fulfilment errors whenever financing is rejected.

---

Three Tamara API Prerequisites Developers Frequently Miss

1. Saudi Phone Number Formatting

Tamara validates Saudi phone numbers during customer verification.

Numbers should always follow Saudi international formatting.

Correct example:

+9665XXXXXXXX

Incorrect formatting frequently causes verification failures that appear as generic API validation errors.

---

2. Unique Merchant Reference IDs

Every checkout session must have a unique merchant reference.

Reusing order numbers across multiple checkout attempts often produces silent duplicate-session rejection.

A better approach is:

ORDER-10452-SESSION-01

instead of simply:

ORDER-10452

This preserves complete audit history while preventing duplicate validation failures.

---

3. Line Item Totals Must Match Exactly

Tamara validates every financial calculation.

The following must reconcile perfectly:

• Product totals
• Shipping
• Discounts
• VAT
• Grand total

Even a SAR 0.01 rounding difference can cause checkout validation failures.

Always calculate totals server-side rather than relying on frontend arithmetic.

---

Step 4 — BNPL Widget Placement Matters More Than Most Merchants Think

One of the biggest misconceptions is that BNPL begins during checkout.

It does not.

Saudi shoppers often decide whether they can afford a purchase while viewing the product itself.

That makes Product Detail Page (PDP) widgets considerably more valuable than merchants expect.

Recommended placement:

Product Page

Immediately below the product price:

Pay in 4 interest-free payments of SAR 250 with Tamara

Shopping Cart

Display updated instalment amounts based on the total basket value.

Checkout

Present Tamara as one of the available payment methods alongside:

• mada
• Apple Pay
• Visa
• Mastercard
• STC Pay
• Tabby

Displaying instalment options early significantly increases purchase confidence for higher-value products.

---

Step 5 — ZATCA Compliance for Tamara Orders

Many merchants assume that because the customer pays over four instalments, VAT should also be split.

This is incorrect.

For Saudi tax purposes, the taxable supply occurs when the order is confirmed—not when future instalments are collected.

That means every successful Tamara transaction should immediately trigger the standard ZATCA Phase 2 workflow.

The process should be:

Customer approved →

Tamara sends order.approved →

Merchant creates ZATCA XML →

Digital signature applied →

Invoice submitted through Fatoora →

Invoice archived →

Customer receives confirmation.

Important compliance rules include:

• Invoice date = order confirmation date
• VAT calculated on the full order amount
• Installment schedule has no effect on VAT timing
• Fatoora clearance follows the same workflow as any other online payment

If your platform already supports mada or STC Pay, Tamara orders should follow the same invoicing pipeline.

The financing method changes.

The tax treatment does not.

---

How to Integrate Tabby into a Saudi E-Commerce Checkout

Although the integration flow resembles Tamara, Tabby introduces several implementation differences that developers should understand before writing code.

Since relocating its headquarters to Saudi Arabia in 2024 and expanding its local operations, Tabby has become one of the Kingdom's largest BNPL providers and now serves merchants across Saudi Arabia, the UAE, Kuwait, and Bahrain.

For Saudi merchants, supporting both providers generally delivers the highest approval coverage.

---

Step 1 — Tabby Merchant Account Setup

The onboarding process begins through the Tabby Merchant Portal.

Typical requirements include:

• Saudi Commercial Registration (CR)
• VAT certificate
• Corporate Saudi bank account
• Business verification documents
• Product catalogue review
• Website compliance review

Businesses already processing payments through Checkout.com may also gain access to Tabby through Checkout.com's single BNPL integration layer, reducing implementation effort.

After merchant approval, Tabby issues sandbox credentials for API development and testing.

How to Integrate Tabby into a Saudi E-Commerce Checkout

Step 1 — Tabby Merchant Account Setup for Saudi Arabia

Tabby has positioned Saudi Arabia as one of its primary markets following the relocation of its headquarters to the Kingdom in 2024. Saudi merchants can apply directly through the Tabby Merchant Portal after completing business verification.

Merchant onboarding generally requires:

• Saudi Commercial Registration (CR)
• Saudi VAT Registration Certificate
• Saudi corporate bank account
• Company ownership documentation
• Business website or mobile application
• Product catalogue review

Businesses already using Checkout.com also have an alternative route. Following the Checkout.com–Tabby partnership announced in 2025, merchants can activate Tabby through their Checkout.com payment stack without implementing an entirely separate payment gateway, simplifying deployment for enterprise stores.

Sandbox credentials are normally issued once merchant verification has been completed.

---

Step 2 — Tabby API Integration

Like Tamara, Tabby uses a REST-based checkout session architecture.

A customer selecting Tabby at checkout is redirected into Tabby's approval workflow before returning to the merchant's website once financing has been approved or declined.

A standard implementation consists of:

1. Customer chooses Tabby.
2. Merchant server creates checkout session.
3. Tabby performs customer verification.
4. Customer approves installment plan.
5. Merchant receives webhook confirmation.
6. Order proceeds through fulfilment.
7. ZATCA invoice is generated.

Typical information sent includes:

• Order amount (SAR)
• Currency
• Merchant reference ID
• Customer name
• Saudi mobile number
• Email
• Shipping address
• Billing address
• Line items
• Tax amounts
• Discounts
• Delivery charges

Tabby's API then returns a checkout URL or embedded checkout token depending on the selected implementation model.

---

Step 3 — Handle Tabby Webhooks Properly

Many integrations fail because developers only listen for successful approvals.

A production-ready implementation should process every webhook state.

Common webhook events include:

Webhook	Action
CLOSED	Approve order and begin fulfilment
EXPIRED	Restore inventory and notify customer
REJECTED	Offer another payment method
CANCELLED	Cancel pending order
REFUNDED	Synchronise accounting and ERP

Webhook validation should always include signature verification before updating order status.

Without webhook validation, attackers could potentially spoof payment confirmations.

---

Step 4 — Three Technical Details Developers Frequently Miss

Several implementation mistakes repeatedly appear during Saudi BNPL projects.

1. Category Restrictions

Tabby applies restrictions to certain product categories depending on merchant agreements and regulatory requirements.

Before displaying BNPL availability across every product, merchants should verify category eligibility rather than assuming universal approval.

Product-level eligibility checks improve customer experience and reduce unnecessary checkout failures.

---

2. Currency Handling

Saudi transactions should always be submitted in SAR.

International platforms operating multiple currencies sometimes accidentally submit USD or AED because the storefront currency differs from the checkout currency.

Explicitly passing SAR prevents unnecessary validation failures.

---

3. Approval Waiting State

Tabby's credit evaluation typically completes within three to eight seconds.

During this period the checkout should display a clear processing state instead of appearing frozen.

Customers frequently abandon checkouts when nothing appears to happen after pressing "Continue."

A proper loading interface significantly improves completed BNPL sessions.

---

Step 5 — Running Tamara and Tabby Together

One of the biggest misconceptions is that merchants must choose one BNPL provider.

For Saudi-focused platforms, the strongest approach is usually integrating both.

A recommended checkout priority looks like this:

1. Tamara
2. Tabby
3. mada
4. Apple Pay
5. STC Pay
6. Credit/Debit Cards

Tamara generally delivers stronger approval rates among Saudi consumers, particularly first-time BNPL users.

Tabby performs exceptionally well among returning Tabby customers and shoppers who already use its ecosystem across GCC merchants.

Offering both increases total approval coverage while giving shoppers flexibility.

---

SAMA Compliance for Saudi BNPL Integration

Saudi BNPL is regulated by the Saudi Central Bank (SAMA).

Merchants should integrate only SAMA-authorised providers.

As of 2026, Tamara and Tabby both operate under SAMA's regulatory framework, providing merchants with compliant consumer financing solutions.

Regulatory compliance extends beyond selecting an approved provider.

Merchants also have responsibilities regarding transparency during checkout.

Customers should clearly see:

• installment amounts,
• payment schedule,
• applicable fees,
• late payment consequences,
• provider terms,
• refund policy.

These details should appear before the customer confirms the purchase.

Hidden financing information increases regulatory risk while reducing customer trust.

---

BNPL and PDPL

During BNPL approval, providers perform identity verification using customer information such as:

• name,
• phone number,
• address,
• payment details,
• identity verification.

Merchants should avoid storing unnecessary verification information inside their own systems.

Instead, the ecommerce platform should retain only:

• BNPL provider,
• transaction ID,
• approval status,
• order reference,
• webhook history.

Sensitive verification remains with the licensed BNPL provider, helping reduce PDPL compliance exposure.

---

BNPL Integration for Custom Saudi E-Commerce Platforms vs Shopify

Choosing between a custom platform and Shopify affects how much flexibility merchants have during BNPL implementation.

Feature	Custom Platform	Shopify
Tamara API	Full control	App-based
Tabby API	Full control	App-based
Checkout UI	Fully customizable	Limited
Widget placement	Unlimited	Limited by theme
ZATCA integration	Native	Requires additional solution
ERP integration	Native	Limited
Marketplace support	Excellent	Moderate
Enterprise workflows	Excellent	Limited

Custom platforms allow developers to build the checkout exactly as required.

Product page widgets, checkout placement, ERP integration, warehouse workflows, loyalty systems, and ZATCA invoicing all operate from one architecture.

Shopify offers faster deployment but sacrifices significant flexibility, especially for enterprise Saudi retailers requiring custom workflows.

---

5-Step BNPL Integration Checklist for Saudi E-Commerce Platforms

Before launching BNPL, every Saudi ecommerce platform should complete the following checklist.

Step 1

Register merchant accounts with Tamara and Tabby.

Complete KYB verification using:

• Commercial Registration
• VAT Certificate
• Saudi corporate bank account
• ownership documents

---

Step 2

Integrate Tamara first.

Implement:

• checkout session creation,
• webhook processing,
• product page widget,
• checkout payment option,
• sandbox testing.

---

Step 3

Verify ZATCA compliance.

Every successful BNPL approval should automatically generate:

• Fatoora XML,
• cryptographic stamp,
• QR code,
• clearance submission,
• accounting entry.

Deferred payment never delays tax invoice generation.

---

Step 4

Add Tabby.

Reuse much of the existing webhook architecture while accounting for:

• approval differences,
• category restrictions,
• currency validation,
• loading states.

---

Step 5

Review Arabic user experience.

Verify:

• RTL layouts,
• Arabic translations,
• SAR formatting,
• widget placement,
• error messages,
• installment calculations.

A technically correct integration can still underperform if the checkout feels unfamiliar to Saudi shoppers.

BNPL Integration for Custom Saudi E-Commerce Platforms vs Shopify

Choosing the right implementation approach depends on how much control you need over the checkout experience, payment orchestration, ZATCA compliance, and future platform expansion.

For merchants building a long-term Saudi e-commerce business, the decision is rarely about whether BNPL should be supported. It is about whether the platform architecture allows BNPL providers to become first-class payment methods rather than third-party plugins.

Custom Platform Integration

A custom-built Saudi e-commerce platform communicates directly with the Tamara and Tabby REST APIs.

Instead of relying on marketplace plugins, the checkout service controls every stage of the customer journey, including eligibility checks, payment selection, webhook processing, tax invoice generation, and order fulfilment.

Typical architecture includes:

Customer Checkout

↓

Payment Service

↓

Tamara API
Tabby API
mada Gateway
Apple Pay
STC Pay

↓

Order Management

↓

ZATCA Invoice Engine

↓

ERP / Inventory

Advantages include:

• Complete control over checkout UX
• Custom Arabic-first interface
• Product-specific BNPL eligibility logic
• Multiple BNPL providers in one checkout
• Centralised payment orchestration
• Native integration with ERP and inventory
• Direct webhook processing
• Custom fraud monitoring
• Better performance than plugin-based integrations

Because the merchant owns the checkout logic, every approved BNPL transaction immediately updates inventory, creates accounting entries, triggers fulfilment workflows, and generates a ZATCA Phase 2 invoice without relying on multiple disconnected apps.

For Saudi marketplaces, enterprise retailers, automotive stores, furniture brands, electronics retailers, healthcare platforms, and luxury commerce, this architecture usually delivers the best operational outcome.

Development effort typically ranges from 2–3 weeks per BNPL provider when starting from an existing custom checkout, including:

• API integration
• Webhook handling
• Sandbox testing
• Arabic localisation
• ZATCA integration
• Error handling
• Approval-state management

---

Shopify Integration

Shopify merchants have a much faster deployment path.

Both Tamara and Tabby provide official Shopify applications that simplify merchant onboarding.

Installation usually consists of:

1. Installing the official app
2. Connecting the merchant account
3. Enabling BNPL inside Shopify checkout
4. Configuring widget placement
5. Testing checkout

This works well for smaller merchants that need speed over flexibility.

However, there are trade-offs.

Shopify limits how much merchants can customise:

• checkout logic,
• widget positioning,
• payment orchestration,
• customer eligibility workflows,
• and advanced post-payment automation.

Merchants should also remember an important Saudi compliance point.

Shopify invoices are not automatically ZATCA Phase 2 compliant.

A Saudi Shopify store still requires either:

• a dedicated ZATCA application, or
• a custom Fatoora integration,

to generate cryptographically signed XML invoices for every completed sale.

BNPL does not remove this obligation.

---

Which Option Is Better?

Requirement	Custom Platform	Shopify
Full checkout control	✓	Limited
Native Tamara API	✓	Via app
Native Tabby API	✓	Via app
Advanced widget customisation	✓	Limited
Marketplace support	✓	Difficult
ERP integration	✓	Limited
Multi-vendor support	✓	Difficult
Native ZATCA workflow	✓	Requires additional solution
Best for enterprise	✓	No
Fastest deployment	No	✓

For growing Saudi businesses planning to expand into marketplaces, omnichannel commerce, ERP integration, or advanced customer journeys, a custom platform usually becomes the preferred long-term option.

---

5-Step BNPL Integration Checklist for Saudi E-Commerce Platforms

A successful Saudi BNPL implementation is much more than connecting two APIs.

Every stage—from merchant onboarding to invoice generation—must be tested against Saudi operational and regulatory requirements.

Step 1 — Register Merchant Accounts

Complete merchant onboarding with both providers.

Prepare:

• Saudi Commercial Registration (CR)
• VAT certificate
• Saudi corporate bank account
• Merchant verification documents
• Business website

Both Tamara and Tabby complete Know Your Business (KYB) verification before issuing production credentials.

---

Step 2 — Integrate Tamara First

For Saudi-first merchants, Tamara generally delivers higher approval rates.

During implementation:

• configure sandbox,
• build checkout session creation,
• process approval webhooks,
• integrate PDP widget,
• test declined scenarios,
• verify expired sessions,
• validate Arabic checkout.

Only move to production after sandbox approval.

---

Step 3 — Verify ZATCA Compliance

Every approved BNPL order must trigger exactly the same taxation workflow as any other payment method.

Your system should automatically:

• generate XML invoice,
• calculate VAT,
• apply cryptographic signature,
• submit to Fatoora,
• store invoice UUID,
• return invoice reference to ERP.

BNPL should never bypass your invoicing engine.

---

Step 4 — Add Tabby

Once Tamara is operating correctly, add Tabby.

Reuse most of the existing architecture while accounting for provider-specific differences including:

• webhook payloads,
• approval states,
• category restrictions,
• eligibility logic,
• error handling.

Running both providers together provides broader customer coverage.

---

Step 5 — Perform Arabic UX Review

Before launch, verify the complete customer journey in Arabic.

Review:

• RTL rendering
• Arabic typography
• installment calculations
• SAR formatting
• widget responsiveness
• approval messages
• declined-payment messaging
• checkout accessibility

Many technically successful integrations still lose conversions because Arabic presentation receives insufficient attention.

---

Example BNPL Installment Breakdown

Order Value (SAR)	Tamara (4 Payments)	Tabby (4 Payments)
SAR 200	SAR 50	SAR 50
SAR 500	SAR 125	SAR 125
SAR 1,000	SAR 250	SAR 250
SAR 2,000	SAR 500	SAR 500
SAR 5,000	SAR 1,250	SAR 1,250

Showing these installment amounts directly on the product page helps customers understand affordability before reaching checkout, which contributes significantly to higher conversion rates.

---

Final Thoughts

Saudi consumers increasingly expect flexible payment options as a standard part of online shopping.

A checkout that supports only cards and cash-on-delivery now feels incomplete when compared with competitors offering Tamara and Tabby alongside mada, Apple Pay, and STC Pay.

For Saudi-focused merchants, the recommended rollout is straightforward:

• Integrate Tamara first for stronger local approval rates.
• Add Tabby to maximise approval coverage.
• Connect every BNPL transaction to your ZATCA Phase 2 invoicing workflow.
• Build Arabic-first checkout experiences from day one.
• Test the entire customer journey—not just the API.

Whether you are building a Shopify store, a marketplace, or a fully custom commerce platform, BNPL should be treated as part of your checkout architecture rather than an optional payment add-on.

At Logiolegion, we build custom Saudi e-commerce platforms with native integrations for Tamara, Tabby, ZATCA Phase 2, mada, STC Pay, ERP systems, and Arabic-first checkout experiences.

If you're planning a Saudi-focused commerce platform, book a free discovery call with Logiolegion at:

https://logiolegion.com/contact-us

We'll help you design a payment architecture that matches Saudi consumer behaviour, regulatory requirements, and future business growth.

Frequently Asked Questions

1. How do I integrate Tamara into a Saudi e-commerce checkout?

To integrate Tamara, you first need a Saudi Commercial Registration (CR), VAT certificate, and a Saudi corporate bank account. After merchant approval, Tamara provides sandbox API credentials that allow your development team to implement checkout sessions, payment widgets, webhook handling, and production deployment.

A complete integration should also include ZATCA Phase 2 invoice generation immediately after the order.approved webhook and Arabic RTL widget testing before launch.

---

2. How do I integrate Tabby into a Saudi e-commerce checkout?

Tabby integration follows a similar API-driven workflow. Merchants register through Tabby's merchant portal or access Tabby through Checkout.com's payment ecosystem if they already use that gateway.

The implementation includes checkout session creation, webhook processing, Arabic checkout support, eligibility handling, and proper SAR currency validation throughout the payment flow.

---

3. Should I use Tamara or Tabby for a Saudi e-commerce store?

For Saudi-first businesses, Tamara should generally be integrated first.

Tamara has stronger approval rates inside Saudi Arabia, a Saudi-native merchant ecosystem, and a full SAMA consumer finance licence. Tabby should then be added to maximise approval coverage, particularly for returning Tabby users and merchants expanding across the GCC.

Running both providers together usually delivers the highest checkout conversion.

---

4. Is BNPL regulated by SAMA in Saudi Arabia?

Yes.

Buy Now Pay Later (BNPL) providers operating in Saudi Arabia must comply with the Saudi Central Bank (SAMA) regulatory framework. Tamara and Tabby are both licensed to operate within Saudi Arabia, making them the preferred BNPL providers for Saudi merchants.

Using unlicensed BNPL providers may expose businesses to regulatory and operational risks.

---

5. Do BNPL transactions in Saudi Arabia require ZATCA invoicing?

Yes.

A BNPL purchase is still considered a taxable supply.

Once Tamara or Tabby approves the transaction, your platform should immediately generate a ZATCA Phase 2 compliant invoice, submit it to Fatoora where required, and store the invoice reference exactly as it would for a standard mada or credit card transaction.

The invoice date is based on the date of supply—not the customer's installment schedule.

---

6. What are the merchant discount rates (MDR) for Tamara and Tabby in Saudi Arabia?

Merchant Discount Rates generally range between 3% and 6%.

The exact rate depends on:

• annual processing volume,
• merchant category,
• average order value,
• commercial negotiations,
• and contract duration.

Although BNPL carries a higher MDR than traditional card payments, many merchants recover the additional cost through increased conversion rates and larger average order values.

---

7. Can I run Tamara and Tabby together in my Saudi checkout?

Yes.

Many enterprise Saudi retailers offer both providers simultaneously.

The recommended implementation is:

• Tamara as the primary Saudi BNPL provider,
• Tabby as the secondary provider for additional customer coverage.

This improves approval rates while giving shoppers flexibility based on their preferred BNPL account.

---

8. What is the minimum order value for BNPL in Saudi Arabia?

The minimum basket value depends on each provider's current merchant agreement.

Eligibility thresholds can vary by:

• merchant category,
• customer profile,
• campaign,
• and provider policies.

Your checkout should validate eligibility before customers begin the approval process to minimise declined applications and abandoned carts.

---

9. Is Tamara Sharia-compliant for Saudi e-commerce?

Yes.

Tamara positions its BNPL offering as Sharia-compliant by providing interest-free installment plans for customers who make payments on time.

Merchants should still display Tamara's current terms and conditions during checkout so customers understand repayment schedules and any applicable late-payment policies.

---

10. What Saudi bank account do I need to accept Tamara and Tabby payments?

Merchants normally require a Saudi corporate bank account registered under their legal business entity.

Common banking partners include:

• Saudi National Bank (SNB)
• Al Rajhi Bank
• Riyad Bank
• Banque Saudi Fransi
• SAB
• Arab National Bank
• Bank AlJazira

During merchant onboarding, Tamara and Tabby verify bank ownership alongside Commercial Registration (CR), VAT registration, and business identity documents before enabling production access.

---

Conclusion

Saudi BNPL is no longer an optional payment method.

With Saudi consumers increasingly choosing interest-free installment payments, merchants that support Tamara and Tabby typically see stronger checkout conversion, higher average order values, and improved customer satisfaction.

A successful implementation goes beyond connecting APIs. It requires SAMA-compliant provider selection, Arabic-first checkout design, proper webhook handling, ZATCA Phase 2 invoice generation, PDPL-aware customer data handling, and continuous testing across the full payment journey.

For Saudi-focused online stores, the recommended approach is clear:

• Integrate Tamara first for stronger Saudi approval rates.
• Add Tabby to maximise approval coverage.
• Connect every BNPL transaction to your ZATCA invoicing workflow.
• Build Arabic-first product pages with installment messaging before checkout.
• Test every approval, decline, cancellation, and refund scenario before going live.

At Logiolegion, we build custom Saudi e-commerce platforms with native integrations for Tamara, Tabby, mada, Apple Pay, STC Pay, ERP systems, and ZATCA Phase 2 compliance.

If you're planning to launch or upgrade your Saudi e-commerce platform, book a free discovery call with Logiolegion:

https://logiolegion.com/contact-us