How to Build a Split Payments App Like Tamara for the MENA Market

Building a split payments app like Tamara for the MENA market costs $30,000 to $50,000 for a focused MVP and $150,000 to $300,000+ for a regulated production platform. What makes a Tamara-style build different from a generic BNPL app is the region: Saudi and UAE licensing, Arabic and right-to-left design, local payment rails, and a Sharia-compliant, interest-free model.

Key takeaways

A split payments app like Tamara costs $30,000 to $50,000 (MVP) up to $150,000 to $300,000+ (regulated production). In local terms that is roughly SAR 112,500 to 1,125,000+ or AED 110,000 to 1,102,000+. Tamara and Tabby lead BNPL across Saudi Arabia and the UAE, the two markets that shape a MENA build. MENA is a distinct build: Arabic and right-to-left UI, AED and SAR currency, local rails like mada, and a Sharia-compliant, interest-free installment model. Regulation is real: SAMA licenses BNPL providers in Saudi Arabia and the Central Bank of the UAE oversees the sector. SolGuruz builds the software; the license stays with you or a partner. SAR and AED are pegged to the US dollar, so local pricing stays stable and predictable.

Tamara is the Saudi-founded BNPL leader that lets shoppers split a purchase into interest-free installments, with a real-time approval at checkout. It operates across Saudi Arabia, the UAE, and Kuwait, alongside Tabby as the other major regional player. If you are building for the Gulf, this guide covers what a comparable app costs and, more importantly, what the region demands that a generic BNPL guide leaves out.

The MENA BNPL opportunityCopy link to "The MENA BNPL opportunity"

BNPL has grown faster in the Gulf than almost anywhere else, driven by a young, mobile-first population and high card and wallet adoption. Saudi Arabia and the UAE are the anchor markets, which is why both Tamara and Tabby built there first before expanding across the GCC.
Two things make the opportunity real rather than hype. First, the shopper base is large and digital-native, so installment checkout converts well. Second, the regulators have moved from a grey area to clear licensing, which raises the bar for new entrants but also legitimizes the market for the ones who build to comply. A serious Tamara-style product is now a regulated fintech build, not a checkout widget.

What makes a MENA BNPL app differentCopy link to "What makes a MENA BNPL app different"

This is the part a generic split-payments guide skips, and it is where most of the real work sits. A Tamara-style app has to feel native to the Gulf, not translated into it.

• Arabic and right-to-left (RTL) design: The entire interface, not just the copy, has to work right-to-left: layout, navigation, forms, and numerals. RTL is a build decision that touches every screen, so it belongs in the design system from day one, not bolted on later.
• AED and SAR multi-currency: The app has to price, charge, and settle in local currency, with clean handling for cross-border shoppers. Because both currencies are pegged to the US dollar, the accounting stays predictable.
• Sharia-compliant, interest-free model: Tamara markets itself as Sharia-compliant, and the interest-free installment structure is central to that. The software has to support a no-interest, fee-transparent model rather than an interest-bearing loan. SolGuruz builds software that supports this model; the Sharia certification itself is a scholarly and product decision on your side, not a software claim.
• Local payment rails: Real regional coverage means integrating local methods: mada in Saudi Arabia, plus cards, Apple Pay, and bank transfers across the UAE. Merchant settlement has to work with local acquirers.

The MENA regulatory landscapeCopy link to "The MENA regulatory landscape"

BNPL in the Gulf is regulated, and building to comply is a cost and a schedule item you plan from the start.

• Saudi Arabia (SAMA): The Saudi Central Bank (SAMA) regulates BNPL and requires providers to be licensed, with rules covering consumer protection, disclosure, and credit conduct.
• UAE (CBUAE): The Central Bank of the UAE oversees finance activity in the UAE, and BNPL providers operate under its financial-services framework.

The honest framing, the same one we apply to every fintech build: SolGuruz builds the software, not the license. The BNPL or finance license sits with you or a licensed partner, and we build the product to comply with the applicable SAMA and CBUAE requirements. We are not a lender or a licensing authority, and no software vendor should imply otherwise. What we do bring is production experience in BNPL app development, building to bank-grade practices, including PCI-DSS Level 1 practices and independent penetration testing, which is what the FlexiPe BNPL build shipped with.

Core features of a split payments app like TamaraCopy link to "Core features of a split payments app like Tamara"

The feature set is close to any BNPL product, with MENA-specific handling layered on. Keep the first version lean, and spend the depth on the credit engine and compliance, because those two decide whether the product survives.

• Onboarding and KYC: Fast sign-up with identity verification tuned for Saudi (Nafath, Absher) and UAE (Emirates ID, UAE Pass) digital identity, plus local KYC and AML providers. The flow has to clear a genuine customer in seconds while catching fraud and meeting regulator requirements, so it is far more than a sign-up form. Expect edge cases around expatriate residents, multiple IDs, and document quality.
• Split payment scheduling: The pay-in-4 or installment engine that divides a purchase into scheduled, interest-free payments, takes the first charge at checkout, and runs the repayment calendar. Rescheduling, partial payments, and late-fee handling all have to fit a Sharia-compliant, fee-transparent model rather than an interest-bearing loan.
• Credit assessment and decisioning: Real-time approve or decline, dynamic spending limits, and risk models trained on local repayment behaviour and bureau data (for example SIMAH in Saudi Arabia and Al Etihad Credit Bureau in the UAE). This is the most defensible and most expensive part of the build, and it is what keeps defaults down as volume grows.
• Merchant integration and dashboard: A checkout plugin or SDK plus a merchant portal for orders, settlements, refunds, and reconciliation. Integration with local acquirers and the e-commerce platforms merchants actually use (Salla, Zid, WooCommerce, Shopify) decides how fast you can sign merchants and how much support they need.
• Payment gateway and rails: Secure processing across mada, cards, Apple Pay, and bank transfers, with PCI-DSS Level 1 practices, tokenization, and settlement that reconciles every payout and fee to the cent. This layer is where fraud and reconciliation errors turn into real losses.
• Notifications and reminders: Approval and decline messages, payment reminders, and status updates over push, SMS, and email, in Arabic and English, timed to cut missed payments. Reminder timing is a genuine lever on default rates, not a cosmetic feature.
• Support and dispute handling: Bilingual in-app support, a clear dispute and refund path, and the audit trail regulators expect for consumer-protection compliance. Disputes touch the ledger, so this connects back to settlement and reconciliation.

How to build a split payments app like TamaraCopy link to "How to build a split payments app like Tamara"

The process is a standard fintech build with the MENA layer folded in. Validate fast, then deepen the parts that carry risk.

1. Research the market and the rules. Pick your launch markets (Saudi, UAE, or wider GCC), map the SAMA and CBUAE licensing and consumer-protection requirements, and study how Tamara and Tabby structure their products and merchant offers. This step decides your licensing path, your data model, and your compliance budget, so it comes first, not as an afterthought. A wrong assumption here is the most expensive mistake you can make.
2. Define your model and monetization. Lock the interest-free structure, the merchant-fee economics, the late-fee policy, and the credit-limit strategy that fit a Sharia-compliant product. Settle this before design, because it directly shapes the decisioning engine, the disclosures, and the regulator conversation.
3. Build a prototype. Validate the core installment flow and the Arabic right-to-left experience with real users before committing to the full build. A rapid PoC development approach compresses weeks of early work, tests the risk model on sample data, and de-risks the direction before the budget grows.
4. Assemble a fintech-savvy team. You need engineers who have shipped regulated fintech, a risk or credit specialist, a compliance lead who knows the SAMA and CBUAE frameworks, and Flutter or native mobile developers who can build a true right-to-left interface rather than a mirrored one.
5. Develop, integrate, and test in tight cycles. Build the credit engine, payment rails, merchant tools, and compliance workflows together, with the Arabic RTL app tested alongside them each cycle. Security testing and PCI-DSS practices run throughout the build, not as a final gate, because retrofitting them is slow and costly.
6. Launch, learn, and iterate. Start in one market, tune the decisioning against real repayment data, watch defaults and fraud closely in the first months, then expand market by market across the GCC once the risk model holds.

Cost to develop a split payments app like TamaraCopy link to "Cost to develop a split payments app like Tamara"

Cost tracks scope, not screens. Below are the same bands we quote for any BNPL build, shown in US dollars (our reference figure) alongside Saudi riyal and UAE dirham.

Build stage	USD	SAR	AED
Focused MVP	$30,000 to $50,000	SAR 112,500 to 187,500	AED 110,000 to 184,000
Growth platform	$50,000 to $150,000	SAR 187,500 to 562,500	AED 184,000 to 551,000
Regulated production	$150,000 to $300,000+	SAR 562,500 to 1,125,000+	AED 551,000 to 1,102,000+

USD is our reference figure. SAR and AED are pegged to the US dollar (1 USD = 3.75 SAR and 1 USD = 3.6725 AED), so local pricing stays stable rather than moving day to day. Rates last checked 2026-07-28. Other GCC currencies (KWD, QAR, BHD, OMR) are also USD-pegged, so you can convert the same way at their fixed rates.
The biggest cost drivers are the credit-decisioning engine, the SAMA and CBUAE compliance work, and the MENA localization (Arabic RTL, local rails). Timelines run 2 to 4 months for an MVP, 4 to 8 months for a growth platform, and 8 to 14 months for a regulated production build. Ranges are indicative and depend on your feature set, markets, and integrations. We give a line-item estimate during scoping, and for a tailored number our BNPL cost calculator produces an estimate inside these bands.
For a US-market view of the same numbers, see our cost to build a BNPL app like Affirm breakdown, and for the generic build steps our how to build a BNPL app guide.

How SolGuruz builds BNPL productsCopy link to "How SolGuruz builds BNPL products"

SolGuruz builds complete BNPL products, from onboarding to settlement, and we have shipped one to production. FlexiPe is a BNPL platform we built with a real-time installment flow, credit decisioning, KYC and AML, and PCI-DSS Level 1 practices. Read the full FlexiPe BNPL app case study for the architecture and compliance detail, and compare a branded build in our BNPL app like Klarna guide.

Ready to build for the Gulf? Talk to our BNPL app development team for a line-item estimate scoped to your markets, currencies, and compliance needs.

FAQsCopy link to "FAQs"

1. How much does it cost to build a split payments app like Tamara?

Expect $30,000 to $50,000 for a focused MVP and $150,000 to $300,000+ for a regulated production build, with a growth-stage platform in between at $50,000 to $150,000. In local terms that is roughly SAR 112,500 to 1,125,000+ or AED 110,000 to 1,102,000+.

2. Why show the cost in SAR and AED as well as USD?

USD is our reference figure and stays fixed. SAR and AED are pegged to the US dollar (1 USD = 3.75 SAR and 3.6725 AED), so the local amounts are a stable conversion rather than a daily-moving rate.

3. Do I need a license to launch a BNPL app in Saudi Arabia or the UAE?

Yes. SAMA licenses BNPL providers in Saudi Arabia and the Central Bank of the UAE oversees the sector in the UAE. The license stays with you or a licensed partner. A software partner like SolGuruz builds the product to comply; it does not act as the lender.

4. What makes a MENA BNPL app different to build?

Arabic and right-to-left design across every screen, AED and SAR multi-currency, local payment rails like mada, a Sharia-compliant interest-free model, and building to SAMA and CBUAE requirements.

5. How long does it take to build a split payments app like Tamara?

Around 2 to 4 months for an MVP, 4 to 8 months for a growth platform, and 8 to 14 months for a full, compliance-heavy production build.