{"id":22551,"date":"2026-04-28T13:47:30","date_gmt":"2026-04-28T13:47:30","guid":{"rendered":"https:\/\/engineerbabu.com\/blog\/?p=22551"},"modified":"2026-04-28T13:47:30","modified_gmt":"2026-04-28T13:47:30","slug":"blog-bnpl-app-development-like-tamara","status":"publish","type":"post","link":"https:\/\/engineerbabu.com\/blog\/blog-bnpl-app-development-like-tamara\/","title":{"rendered":"How to Build a BNPL App Like Tamara \u2014 The Saudi BNPL Opportunity Nobody’s Talking About"},"content":{"rendered":"

Everyone writes about Tabby.<\/p>\n

Tabby is UAE. Tabby is the headline. Tabby is the case study every BNPL blog references. Nobody’s writing about Tamara. And that’s exactly why this blog exists.<\/p>\n

Tamara is the #1 Buy Now Pay Later platform in Saudi Arabia. Strong App Store presence. Deep merchant network across the Kingdom. And it’s operating in the single most interesting fintech market in the Middle East right now.<\/p>\n

Saudi Arabia’s Vision 2030 isn’t a slogan. It’s $3.3 trillion in planned economic transformation. Fintech is a pillar of that transformation. SAMA \u2014 the Saudi Central Bank \u2014 has been actively creating regulatory frameworks for digital payments, BNPL, and open banking. The Saudi fintech ecosystem grew by 37% in 2024 alone.<\/p>\n

And here’s the number that matters most: Saudi Arabia has a population of 36 million people, a median age of 31, smartphone penetration above 97%, and credit card penetration below 25%.<\/p>\n

Young population. Digital-first. Underserved by traditional credit. That’s the exact demographic profile that made BNPL a $309 billion global market.<\/p>\n

Tamara understood this before the rest of the world noticed. But Tamara is one company in a market that can support many. Saudi Arabia isn’t a winner-take-all market \u2014 it’s a market that’s still being built.<\/p>\n

If you’re thinking about BNPL app development for the Saudi market, this is the most important blog you’ll read. Because I’m going to tell you what it actually takes \u2014 not from a feature list, but from having built the systems that power products exactly like this.<\/p>\n

My name is Mayank Pratap. I co-founded EngineerBabu 14 years ago. Here’s who the team has built for.<\/p>\n

EarlySalary \u2014 the lending platform that has disbursed over \u20b910,000 crore. The EngineerBabu team built the credit infrastructure from the ground up. Khatabook \u2014 scaled to tens of millions of Indian SMEs. OpenMoney \u2014 full-stack financial platform unifying payments, investments, and credit. Bank Open \u2014 neobank that became a unicorn, with core banking integrations built by the team. TaptapSend \u2014 multi-continent remittance platform across five regulatory jurisdictions. Kulu Fintech \u2014 GCC-focused financial infrastructure built specifically for Middle East markets. Payment orchestration within the Razorpay ecosystem. Products for Paytm’s ecosystem, Adani Group, and healthcare platforms for Apollo Hospitals, Manipal, Shalby, CHL, ResMed, and 1MG.<\/p>\n

24 unicorn clients. 75 Y Combinator selections. 200+ VC-funded products. 500+ total projects shipped. Google AI Accelerator 2024. CMMI Level 5. Backed by Vijay Shekhar Sharma. LinkedIn Top 20 Startups India. NASSCOM member.<\/p>\n

The team has built fintech products that handle real money in real markets under real regulatory oversight. The Saudi market has specific nuances \u2014 SAMA regulations, SIMAH credit bureau integration, Arabic-first UX, local payment methods \u2014 that generic development teams discover mid-project. The EngineerBabu team has worked in GCC fintech through Kulu Fintech. These nuances aren’t surprises. They’re known variables.<\/p>\n

Why Saudi Arabia Is the Most Interesting BNPL Market Right Now<\/h2>\n

The UAE gets the headlines. Saudi Arabia has the numbers.<\/p>\n

Saudi Arabia’s GDP crossed $1.1 trillion in 2024 \u2014 the largest economy in the Middle East.<\/p>\n

E-commerce in the Kingdom grew 25% year-on-year, reaching $13.6 billion. Digital payment transactions increased by 40% in 2024.<\/p>\n

But credit card penetration remains below 25%. That means 75% of the population \u2014 mostly young, mostly digital-native \u2014 doesn’t have access to traditional credit instruments. They’re buying online. They’re buying in stores. And they’re paying in cash or debit.<\/p>\n

BNPL fills that gap perfectly. Interest-free installments. No credit card required. Instant approval at checkout.<\/p>\n

SAMA has been proactive about regulating BNPL \u2014 which is actually good news for new entrants. Clear regulations mean clear rules of engagement. Companies that build for compliance from day one have an advantage over those that built fast and are now scrambling to retrofit.<\/p>\n

Tamara has first-mover advantage. But first-mover advantage in fintech is temporary. Tamara can’t serve every vertical, every merchant segment, every consumer demographic. There’s room for niche BNPL products \u2014 travel BNPL, healthcare BNPL, B2B BNPL, BNPL for specific merchant categories. There’s room for white-country products that serve the Saudi market with better UX, faster approval, or deeper merchant integration in underserved categories.<\/p>\n

The window is open. It won’t stay open forever.<\/p>\n

What Building BNPL for Saudi Arabia Actually Requires<\/h1>\n

Building a BNPL app for the Saudi market isn’t the same as building one for the UAE, India, or Europe. The fundamentals are similar. The specifics are different. And the specifics are what kill projects that treat “Middle East” as a single market.<\/p>\n

SAMA Compliance \u2014 The Non-Negotiable Starting Point<\/h2>\n

The Saudi Central Bank has issued specific guidelines for BNPL operators. These aren’t suggestions. They’re requirements.<\/p>\n

Capital adequacy requirements. Consumer protection disclosures. Dispute resolution frameworks. Data localization \u2014 consumer financial data must be stored within Saudi Arabia. Reporting obligations to SAMA on portfolio performance, default rates, and consumer complaints.<\/p>\n

Most development teams discover these requirements after they’ve built the product. The cost of discovering compliance requirements late is measured in months and hundreds of thousands of dollars in rearchitecting.<\/p>\n

When the EngineerBabu team built TaptapSend’s remittance platform, they handled compliance across five regulatory jurisdictions simultaneously. Different KYC rules. Different data residency mandates. Different reporting frequencies. One compliance architecture that absorbed all of them. That same compliance abstraction approach \u2014 build the framework once, configure per jurisdiction \u2014 is exactly how the team approaches Saudi BNPL. SAMA compliance isn’t bolted on. It’s baked into the architecture from sprint one.<\/p>\n

CMMI Level 5 certification means this isn’t aspirational language. It’s audited process. Every security decision, every data handling choice, every compliance touchpoint follows internationally certified practices.<\/p>\n

\"\"<\/p>\n

SIMAH Credit Bureau Integration \u2014 The Credit Intelligence Layer<\/h2>\n

SIMAH is Saudi Arabia’s credit bureau. Every BNPL credit decision in the Kingdom runs through SIMAH data.<\/p>\n

Integration with SIMAH isn’t like plugging in an API and reading a score. It requires understanding the data structure SIMAH returns, mapping it to the risk model’s input parameters, handling response latency (the credit decision still needs to happen in under 2 seconds at checkout), and managing the bureau’s availability windows and fallback procedures.<\/p>\n

The CTO at EngineerBabu spent 17 years at Wishfin \u2014 one of India’s largest credit marketplaces. Wishfin integrated with CIBIL, Experian, CRIF, and multiple bureau data sources. The patterns are identical. The data formats differ. The risk logic differs. But the engineering discipline of making a credit bureau integration fast, reliable, and accurate \u2014 that transfers directly from Indian bureaus to SIMAH.<\/p>\n

When the team built EarlySalary’s credit engine, bureau integration was the critical path. The engine processes thousands of credit decisions daily \u2014 pulling bureau data, combining it with alternative signals, and producing an approval decision in real time. That same engineering \u2014 built for speed, accuracy, and reliability \u2014 applies to SIMAH-powered BNPL credit scoring.<\/p>\n

Google’s selection of EngineerBabu for the AI Accelerator 2024 was built around AI-driven credit intelligence. The AI layer sits on top of bureau data, enhancing raw scores with behavioral signals, device fingerprinting, transaction velocity analysis, and merchant risk profiling. The result is a credit engine that makes better decisions than bureau data alone \u2014 approving consumers who deserve credit and declining those who don’t, with the precision that keeps default rates below the threshold where BNPL economics break.<\/p>\n

Arabic-First UX \u2014 Not Translation, Design<\/h2>\n

This is where international development teams consistently fail in Saudi Arabia.<\/p>\n

Arabic isn’t just right-to-left text. It’s a different visual hierarchy. Different scanning patterns. Different form layouts. Different date formats. Different number formatting. Different cultural expectations around trust signals, color associations, and interface metaphors.<\/p>\n

A BNPL app built in English and then “translated” to Arabic will feel foreign to Saudi users. It will feel like what it is \u2014 an afterthought. And in a market where the top apps (Tamara, STC Pay, mada) are Arabic-first, a translated app can’t compete.<\/p>\n

When the Kulu Fintech team needed GCC-specific financial infrastructure, the EngineerBabu team built with Arabic support from the beginning \u2014 not as a localization layer, but as a primary design consideration. Right-to-left layouts. Arabic typography that actually looks beautiful, not just functional. Cultural UI patterns that Saudi users expect.<\/p>\n

Khatabook’s scaling to tens of millions of users across India required similar discipline \u2014 supporting multiple Indian languages, diverse device capabilities, varied literacy levels. The team learned that localization isn’t translation. It’s redesign. That learning applies directly to Saudi BNPL where Arabic-first isn’t a feature. It’s the baseline.<\/p>\n

Merchant Network \u2014 Saudi-Specific Integration<\/h2>\n

The merchant ecosystem in Saudi Arabia has its own characteristics. mada (the national debit card network) is dominant. STC Pay has significant market share. Apple Pay is growing but not universal. Cash on delivery remains relevant in e-commerce.<\/p>\n

A BNPL merchant integration layer for Saudi Arabia needs to support mada payments alongside Visa and Mastercard. It needs to integrate with Saudi e-commerce platforms \u2014 Salla and Zid are more relevant than Shopify in the local market. Physical retail QR-based integration matters because Saudi consumer behavior still skews toward in-store shopping for many categories.<\/p>\n

The merchant dashboard needs Arabic support. Settlement in Saudi Riyals. VAT compliance (15% in Saudi Arabia). SADAD integration for bill-payment use cases.<\/p>\n

The team has built merchant integration layers across multiple products and markets \u2014 including Razorpay ecosystem work and merchant settlement systems for platforms processing significant transaction volumes. The pattern of building SDKs, plugins, APIs, sandbox environments, and merchant dashboards is well-established. The Saudi-specific elements \u2014 mada, Salla, Zid, SADAD, SAR settlement \u2014 are configuration on top of proven architecture.<\/p>\n

\"\"<\/p>\n

The Technology Decisions That Matter for Saudi BNPL<\/h1>\n

The tech stack for a Saudi-focused BNPL app is similar to any BNPL platform \u2014 with critical additions for the local market.<\/p>\n

Flutter for the consumer app \u2014 one codebase for iOS and Android with full RTL (right-to-left) support built into the framework. React for the merchant dashboard with Arabic language support.<\/p>\n

Node.js for the transaction API layer. Python for the credit scoring engine and SIMAH integration logic. PostgreSQL for transactional data. Redis for caching.<\/p>\n

Here’s where Saudi-specific requirements change the infrastructure decisions: data localization requires servers within Saudi Arabia. <\/strong>AWS has a region in Bahrain (closest to Saudi), and GCP has been expanding Middle East presence. Some SAMA-regulated data may require hosting within the Kingdom itself. The architecture must support data residency requirements without compromising performance.<\/p>\n

The microservices approach matters even more in a market with specific regulatory requirements. When SAMA updates reporting requirements \u2014 and they will, the regulatory framework is still evolving \u2014 the reporting service can be updated independently without touching the payment processing or credit decisioning services.<\/p>\n

When the team built Bank Open’s neobank architecture, the same principle applied \u2014 independent services, independent scaling, independent updates. Bank Open became a unicorn. The architecture never became a bottleneck. That’s the kind of foundation a Saudi BNPL product needs.<\/p>\n

How the EngineerBabu Team Approaches Saudi BNPL Development<\/h1>\n

The team starts with regulatory mapping. Not a generic “check the compliance boxes” exercise. A deep mapping of SAMA requirements, SIMAH integration specifications, data residency mandates, consumer protection disclosures, and dispute resolution frameworks. This happens before a single wireframe is drawn.<\/p>\n

Then comes unit economics modeling. What merchant commission rate does the Saudi market support? (Saudi merchants may have different expectations than UAE merchants.) What default rate can the business model absorb? What does the consumer acquisition cost look like in a market where Tamara already has brand recognition? These questions shape product decisions.<\/p>\n

Then design \u2014 Arabic-first, built around Saudi user expectations and behavior patterns. Not a Western app with an Arabic skin.<\/p>\n

Then development \u2014 with compliance, security, and bureau integration built into every sprint. CMMI Level 5 processes ensure that nothing ships without security review and compliance validation.<\/p>\n

Then merchant pilot \u2014 5-10 merchants across different categories. Real transactions. Real money. Real consumer behavior data feeding back into the credit model.<\/p>\n

The team ships MVPs in 8-12 weeks. The Saudi-specific elements \u2014 SIMAH integration, SAMA compliance, Arabic UX, mada payment support \u2014 are known variables, not discovery items. The team has built in the GCC before. Through Kulu Fintech. Through cross-border compliance work on TaptapSend. Through EarlySalary’s bureau-integrated credit engine. The components exist. The expertise exists. The execution is what matters.<\/p>\n

Why Most International Teams Fail in Saudi BNPL<\/h1>\n

Three consistent failure modes.<\/p>\n

Treating Saudi Arabia like “the UAE but bigger.” <\/strong>Different regulator (SAMA vs CBUAE). Different credit bureau (SIMAH vs Al Etihad). Different payment infrastructure (mada dominance).<\/p>\n

Different consumer behavior. Different merchant ecosystem (Salla and Zid, not just Shopify). Different data localization requirements. Teams that build for “the Middle East” generically end up with a product that works well nowhere.<\/p>\n

The EngineerBabu team has built for specific markets \u2014 Kulu Fintech for the GCC, TaptapSend across five specific jurisdictions with specific compliance for each, EarlySalary for India’s specific regulatory environment. The team doesn’t build for regions. They build for markets.<\/p>\n

Underestimating the credit engine. <\/strong>BNPL is a credit product. In Saudi Arabia, with SIMAH integration, local behavioral data, and SAMA reporting requirements, the credit engine is even more critical. Teams that treat the credit engine as “integrate an API and use a threshold score” end up with default rates that destroy the business model within 12 months. The CTO’s 17 years at Wishfin and the team’s experience building EarlySalary’s credit engine \u2014 which has sustained \u20b910,000 crore in disbursals \u2014 means the credit engine gets the engineering depth it deserves.<\/p>\n

Launching without proper Arabic UX. <\/strong>A translated app loses to an Arabic-first app every time in the Saudi market. Saudi consumers have high expectations for app quality \u2014 they use Tamara, STC Pay, SNB’s digital banking app. A BNPL app that feels like a translation project won’t earn trust. Trust is everything in financial products.<\/p>\n

What Clients Get When They Work With EngineerBabu on Saudi BNPL<\/h1>\n

Mayank Pratap leads the company personally. Founder involvement from day one. Architecture reviews, product decisions, scope trade-offs \u2014 the founder is in the room.<\/p>\n

The team builds custom BNPL platforms from scratch. The client owns everything \u2014 code, IP, architecture documents, deployment scripts. No white-label. No shared infrastructure. A product built specifically for the client’s market and business model.<\/p>\n

CTO with 17 years of credit infrastructure experience. Google AI Accelerator 2024 for the AI layer. CMMI Level 5 for audited engineering processes. GCC fintech experience through Kulu Fintech. Multi-jurisdiction compliance experience through TaptapSend. Credit engine experience through EarlySalary (\u20b910,000 Cr+). Scale experience through Khatabook (tens of millions of users).<\/p>\n

24 unicorn clients. 75 Y Combinator selections. 200+ VC-funded products. LinkedIn Top 20 Startups India. Backed by Vijay Shekhar Sharma.<\/p>\n

BNPL app development starting from $15K depending on scope, Saudi-specific compliance requirements, and feature depth. Exact numbers after understanding the specific business.<\/p>\n

\"\"<\/p>\n

Let’s Talk<\/h1>\n

If you’re serious about building a BNPL product for Saudi Arabia, email Mayank directly.<\/p>\n

mayank@engineerbabu.com<\/a>.<\/p>\n

Tell him about the market segment you’re targeting. The merchant categories. The regulatory status. The business model. He’ll spend 30 minutes understanding the business and giving an honest assessment \u2014 does building make sense? What should be built first? What does the Saudi-specific compliance landscape require?<\/p>\n

No pitch deck. No generic proposal. A conversation between people who’ve built fintech products that handle real money in real markets.<\/p>\n

Mayank Pratap <\/strong>Co-founder, EngineerBabu mayank@engineerbabu.com<\/a> | engineerbabu.com<\/p>\n

Google AI Accelerator 2024 \u00b7 CMMI Level 5 \u00b7 Backed by Vijay Shekhar Sharma \u00b7 24 Unicorn Clients<\/em><\/p>\n