From checkout instalments to accounts, cards, and SME credit
On 14 September 2026, Fintech News UAE reported that Tabby raised $233 million in equity at a $6.5 billion valuation, with Blue Pool Capital leading. Founded in the UAE in 2019 and headquartered in Saudi Arabia since 2023, Tabby was MENA’s first fintech unicorn in 2023. The new capital targets expansion beyond buy-now-pay-later into broader financial services in KSA and the UAE — backed by SAMA consumer and SME financing licenses, the acquisition of Tweeq (wallet/accounts/cards/transfers), and a UAE Stored Value Facilities licence enabling Tabby Cash.
For product strategists across the region, Tabby’s path is a template: win a high-frequency surface (checkout), then earn licenses that let you deepen the relationship without rebuilding trust from zero. Valuation follows licensed depth and daily craft — not BNPL volume alone.
License → surface mapping is the real roadmap
Each regulatory win should unlock a concrete UX: longer-tenor financing, working-capital for SMEs, fee-free cash accounts. Announcing “platform” without the flow trains users to ignore you. Dual-market ops between Saudi and UAE rules mean feature flags, residency, and copy variants are product infrastructure — the craft iFynx applies to multi-country launches.
BNPL honesty remains the brand. Clear schedules, Arabic/English disclosures, and dispute paths must not slip while accounts and cards expand. Expansion fails if instalment clarity erodes under the pressure of new product lines.
Builder priorities this quarter
- Map license → product surface. Every regulatory win should ship a measurable activation flow within one sprint cycle of approval communications.
- Keep BNPL UX honest. Schedules, bilingual disclosures, and dispute paths remain the brand while you expand.
- Design for dual-market ops. Saudi and UAE rules diverge; flags and copy variants are infrastructure, not polish.
- Unify identity after acquisition. Tweeq-class stacks need one login story and clear which product owns which balance during migration.
- Instrument SME vs consumer funnels separately. Working-capital UX fails when you reuse consumer instalment copy wholesale.
MENA full-stack fintech checklist
- Per-license activation dashboards (consumer financing, SME, stored value)
- Bilingual instalment schedules that survive screenshot culture
- Dispute and hardship paths before marketing “one money app”
- Migration banners naming legacy wallet vs new cash product
- Credit limit change explanations with human support handoff
- Shared design tokens across checkout, wallet, and SME portals
iFynx takeaway
Valuation follows licensed depth and daily product craft. Treat every new license as a UX sprint with measurable activation — not a press-release destination. iFynx helps teams turn regulatory wins into bilingual surfaces merchants and consumers can trust on Monday morning.
Full-stack without losing the checkout promise
BNPL earned Tabby daily attention at checkout. Accounts, cards, and SME credit only work if that attention still feels honest. Run a standing “instalment clarity” review every sprint: schedule screenshots, Arabic/English fee copy, and dispute entry points must remain one tap away even as Tabby Cash and Tweeq-origin features grow.
Acquisition integration is where most full-stack stories stumble. Users should never wonder which balance pays a purchase. Migration banners, unified statements, and a single support identity are design-systems work — tokens, status vocabularies, and error codes converging before the brand campaign.
For competitors watching from Cairo, Amman, or Dubai, the lesson is sequential licensing mapped to sequential UX — not a big-bang “super app” announcement. Measure activation per license; kill features that do not convert within a defined window.
Operational excellence between KSA and UAE
Dual HQ narratives only work if ops playbooks diverge where regulation diverges and converge where customers expect one brand. Maintain a living matrix: product × market × license × UX surface. Review it in weekly product ops, not only in legal. When Tweeq-origin features and Tabby Cash land, that matrix prevents “which app holds my money?” support tickets from exploding.
SME credit deserves its own onboarding tone. Wholesale reuse of consumer BNPL microcopy creates mismatched expectations on tenors and collateral. Invest in SME-specific empty states, document upload UX, and status vocabularies that finance teams recognise.
Related reading
- Sav’s AI PFM and Saudi expansion
- Zeal’s terminal loyalty approach
- Failed payments without shame
- Fintech UX trust signals
- All featured articles
What “full-stack fintech” means for product architecture
Moving from buy-now-pay-later (BNPL) to accounts, cards, wallets and SME credit is not just adding features. It changes the core of the product. A BNPL app is built around a purchase; a full-stack financial app is built around a customer and their money over time. That shift usually requires:
- A single customer identity across products, so a shopper who started with instalments can open an account or card without onboarding again.
- A shared ledger view that shows balances, instalments, card spending and transfers in one consistent timeline.
- Product-specific compliance layered on top: consumer finance rules for instalments, stored-value or payment rules for wallets, card scheme rules for cards and SME credit rules for business lending.
- Country-specific configuration, since the same brand operates under different licences in Saudi Arabia and the UAE.
Designing the transition for existing users
Millions of users know a BNPL brand as “the way I split payments”. Introducing accounts or cards to them works best when it builds on that habit rather than interrupting it. Practical patterns include offering a wallet balance when a refund is issued, suggesting a card when a user frequently pays in instalments at the same merchants, and explaining each new product in one short screen before asking for any additional information. Avoid pushing every product to every user; relevance matters more than reach.
Responsible credit UX
As BNPL providers move into broader credit, responsible lending design becomes central. Show the total amount owed across all products in one place, make upcoming payments impossible to miss, warn before a purchase would create several overlapping instalment plans, and make it easy to pay early. For SME credit, give business owners a clear view of repayments against expected cash flow. These patterns protect customers and reduce defaults.
Saudi and UAE regulatory context
In Saudi Arabia, consumer and SME financing are licensed and supervised by the Saudi Central Bank (SAMA), and BNPL providers operate under SAMA’s rules for that activity. In the UAE, stored value and payment services fall under the Central Bank’s frameworks. The Saudi Personal Data Protection Law, enforceable since 14 September 2024, and the UAE federal Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) govern how customer data is shared between products. Design data sharing between products with explicit, understandable consent.
Engineering for scale across products
- Separate product services (instalments, wallet, cards, SME lending) behind a common customer and ledger layer.
- Use event-driven architecture so that a payment in one product updates the customer view everywhere.
- Build feature flags by country and licence so launches can be staged safely.
- Invest early in reconciliation and reporting, which grow complex with each new product.
Product metrics for a multi-product fintech
Once an app offers several financial products, single-product metrics stop telling the whole story. Teams should track how many active customers use more than one product, how long it takes a new BNPL user to adopt a second product, and whether cross-product customers repay more reliably. Equally important are negative signals: complaints about unexpected products, rising support contacts, or customers holding overlapping credit lines. Healthy growth shows in deeper relationships, not just more product launches.
Merchant side of the platform
BNPL companies started with merchants, and the merchant experience still matters as the consumer side grows. Merchants need simple integration, fast settlement, clear dashboards of orders, refunds and disputes, and tools to run promotions with the provider. A full-stack strategy often adds merchant products too, such as working capital or payment acceptance. The design challenge is keeping the merchant portal focused while capabilities expand.
Common mistakes when expanding beyond BNPL
- Launching each new product as a separate app experience with its own onboarding.
- Showing promotional offers for credit products at moments of financial stress.
- Hiding the total amount a customer owes across instalments, cards and loans.
- Underestimating the reconciliation and reporting work each new product adds.
- Copying one country’s flows into another market without checking local rules.
Teams that avoid these mistakes build an app customers trust with more of their financial life, which is the real goal of going full-stack.
How iFynx can help
iFynx is a product and engineering team based in Gaza, Palestine that works with clients across the Gulf. We help companies in Saudi Arabia and the UAE design, build and test digital products like the ones discussed here, with Arabic and English interfaces from day one, careful attention to local regulation and data protection, and a focus on measurable outcomes. If you are planning a similar product, we are happy to discuss scope, risks and a realistic first release.
Frequently asked questions
What is a full-stack fintech?
A company that offers several connected financial products, such as payments, accounts, cards and credit, rather than a single service.
Why do BNPL companies expand into accounts and cards?
To serve customers beyond checkout, increase engagement and build more durable revenue from a broader relationship.
How should apps show debt across several products?
In one clear summary of total owed, upcoming payments and due dates, visible from the home screen.
Does the same app need different features by country?
Often yes, because licences and rules differ between Saudi Arabia and the UAE.
Related: Tamara’s Islamic financing and credit UX · Embedded SME lending in the Gulf. Building a fintech app for KSA and the UAE? See app development for Saudi Arabia and app development for the UAE.
