In the GCC ecommerce market (Saudi Arabia, UAE, Kuwait), Buy Now, Pay Later (BNPL) is no longer a conversion optimization tactic—it is baseline infrastructure. If a Saudi consumer reaches your checkout with a basket value over 300 SAR and does not see an option to split the payment across four months, the probability of cart abandonment exceeds 60%.
The dominant players in the region are Tabby and Tamara. Integrating these platforms correctly requires more than just installing a plugin. It requires careful frontend engineering to display the split-payment widgets across the buyer journey, and robust backend engineering to ensure webhooks successfully capture payment authorization without dropping orders. This guide breaks down the engineering reality of BNPL integration across different commerce architectures.
Tabby vs Tamara: The technical and commercial differences
From a consumer perspective, Tabby and Tamara offer nearly identical value propositions: split payments into 3 or 4 interest-free installments. From a merchant and engineering perspective, there are distinct nuances.
Market Coverage: Both cover KSA and UAE aggressively. Tamara currently holds a slight perception edge in Saudi Arabia for local merchants, while Tabby has deeply entrenched itself in the UAE and with large enterprise brands across the GCC.
API Architecture: Both provide modern REST APIs and comprehensive webhook systems. Their integration logic follows a standard asynchronous capture pattern: the customer is redirected to the BNPL hosted checkout, authorizes the payment, and is redirected back to the merchant's success page while a webhook fires in the background to confirm the transaction status.
Fees: Merchant Discount Rates (MDR) for both typically hover between 4% and 7% plus a fixed transaction fee, depending on your volume and negotiation power. It is an expensive payment method, but the 20-40% aggregate lift in conversion rate almost universally outweighs the margin hit.
Shopify Integration Options
Integrating BNPL on Shopify is generally straightforward due to Shopify's modern payments architecture, but the implementation approach depends on your store tier.
Native App Integration: For standard Shopify merchants, Tabby and Tamara provide native payment gateway apps. Installation is frictionless, dropping the payment option seamlessly into Shopify's closed checkout environment. However, injecting the promotional widgets (e.g., "Pay in 4 installments of 50 SAR") on the Product Detail Page (PDP) and Cart drawer often requires theme block configuration or custom Liquid/JavaScript to ensure the widget updates dynamically when a user changes a variant or cart quantity.
Custom API/Headless Approach: If you are running Shopify headlessly via Storefront API, the native apps will not render UI widgets on your Next.js frontend. Your engineering team must manually implement the BNPL promotional widget scripts into your React components, and handle the redirect logic to Shopify's web checkout specifically with the BNPL gateway pre-selected.
WooCommerce Integration
WooCommerce provides ultimate flexibility, which means it also provides ample opportunity for things to break. Both Tabby and Tamara offer official WordPress plugins.
The primary engineering challenge on WooCommerce is theme compatibility. Because every WooCommerce theme handles hooks differently, the BNPL promotional widgets often fail to render in the correct DOM position on the PDP, or fail to update when AJAX add-to-cart events fire. Your engineers will almost certainly need to write custom PHP to unhook the default widget placements and manually inject them into your specific theme template, alongside custom JavaScript to listen for variant change events and re-render the widget pricing.
Wix Integration (And dealing with closed ecosystems)
Integrating GCC-specific gateways into closed platforms like Wix can be highly restrictive. Historically, Wix did not natively support regional BNPL providers via easy plugins, forcing merchants into complex workarounds.
When we engineered a solution for a UAE-based jewellery brand operating on Wix, we had to bypass standard plugin limitations. This involves utilizing Wix Velo (their native JavaScript framework) to build a custom integration via Tabby's API, manually handling the checkout session creation and carefully managing the webhook ingestion to ensure order statuses update correctly in the Wix dashboard. It is a complex engineering task that requires deep familiarity with asynchronous payment flows.
The Testing & QA Checklist
Before pushing a BNPL integration to production, run this strict QA protocol:
- Dynamic Widget Updates: On the PDP, select a higher-priced variant. Does the BNPL widget instantly update to reflect the new installment amount?
- Cart Injection: Does the BNPL widget accurately reflect shipping costs and taxes added at the cart level?
- Webhook Resilience: Simulate a successful BNPL authorization but manually block the redirect back to the store (simulating a customer closing their browser). Does the background webhook still successfully mark the order as "Paid" in your backend?
- Refund Flow: Process a partial refund via your platform's backend (e.g., Shopify admin). Does this automatically trigger the refund API call to Tabby/Tamara, or does it require manual double-entry?
- Currency Limits: Both providers enforce minimum and maximum basket values. Does your checkout gracefully hide the BNPL option if the cart is under 50 SAR or over 5,000 SAR?
Payment infrastructure must be flawless; a dropped webhook means a lost order and a frustrated customer. We build resilient, high-conversion payment architectures for enterprise brands operating across the Middle East. Review our Wix Tabby BNPL Integration case study to see how we solve complex payment routing, or explore our Commerce Platform Engineering capabilities.