Banking-as-a-Service (BaaS): How Non-Bank Apps in Singapore Offer Banking Features
Banking-as-a-Service (BaaS) is a model where a licensed bank provides its regulated infrastructure — accounts, payment rails, card issuing — through APIs to non-bank companies, letting fintechs, retailers, and platforms embed banking features like accounts or cards into their own apps without becoming a licensed bank themselves.
Not financial advice. All figures for educational reference only. Data as at September 2026.
Last updated: September 2026
Key Takeaways
- BaaS lets a non-bank company (a ride-hailing app, e-commerce platform, or fintech startup) offer banking features under its own brand while a licensed bank behind the scenes handles the regulated activity.
- In Singapore, BaaS partnerships must still operate within MAS’s regulatory perimeter — the licensed bank remains accountable for compliance, even though the customer-facing brand may be entirely different.
- BaaS is distinct from open banking: BaaS is about a non-bank offering banking products through a bank partner, while open banking (like SGFinDex) is about securely sharing financial data across institutions.
- Common BaaS use cases in Singapore include embedded wallets in super-apps, co-branded prepaid or debit cards, and buy-now-pay-later providers issuing virtual cards through a bank partner.
- For consumers, the key practical question with any BaaS-powered product is which underlying bank holds the funds and whether SDIC deposit insurance actually applies to the arrangement.
What Is Banking-as-a-Service (BaaS)?
Banking-as-a-Service is an arrangement where a licensed bank exposes core banking capabilities — account opening, fund holding, payment processing, card issuing — through application programming interfaces (APIs) that other companies can plug into. Instead of a fintech startup or retailer spending years and tens of millions of dollars obtaining its own banking licence, it can partner with an existing bank and build a customer-facing product (an app, a card, a checkout flow) on top of the bank’s regulated infrastructure.
The model emerged globally as banks recognised that owning the full customer relationship for every financial product was less valuable than monetising their licensed infrastructure at scale, and as non-bank companies realised customers increasingly expect financial features (save, spend, borrow) embedded directly into the apps they already use daily. In Singapore, BaaS has grown alongside the maturing digital bank ecosystem and MAS’s broader push toward API-driven financial infrastructure, though the regulatory responsibility for any BaaS arrangement always sits with the licensed bank partner, not the non-bank brand consumers interact with.
How Does Banking-as-a-Service Work in Singapore?
In a typical Singapore BaaS arrangement, three parties are involved: the licensed bank (which holds the MAS banking licence and is ultimately accountable for regulatory compliance, AML/CFT, and safeguarding of funds), the BaaS technology or middleware provider (which builds the API layer connecting the bank’s systems to partner businesses, sometimes the bank itself, sometimes a separate fintech infrastructure company), and the non-bank brand (the consumer-facing company — an e-commerce platform, ride-hailing app, or HR payroll platform — that markets the banking feature under its own name).
| Role | Who Holds It | Regulatory Responsibility |
|---|---|---|
| Banking licence | Licensed bank (full or digital bank) | Fully MAS-regulated under the Banking Act |
| API/technology layer | BaaS platform provider (bank or third-party fintech) | Operates under the bank’s compliance oversight |
| Customer-facing brand | Non-bank company (retailer, app, platform) | Generally not itself a licensed bank |
For consumers, this means the app they see and the login they use may belong to a familiar retail or lifestyle brand, but the actual account, card, or payment rail behind it is issued and regulated by a partner bank. In Singapore, this is why the fine print of many co-branded cards or embedded wallet products names a specific issuing bank — that’s the BaaS partner whose licence, capital, and compliance framework the product actually runs on. Consumers should check this fine print to understand whether SDIC deposit insurance genuinely applies to their balance, since coverage depends on the funds being held in an actual deposit account with the licensed bank, not merely routed through it.
Banking-as-a-Service Example
A Singapore-based e-commerce platform wants to offer its sellers a business account and a prepaid card for managing platform earnings and paying suppliers, without becoming a licensed bank itself. Instead of applying for a banking licence — a multi-year, capital-intensive process — the platform partners with a licensed Singapore bank’s BaaS division.
The bank provides the underlying account infrastructure, card issuing (through a card network partnership), and payment rails, all accessible via API. The e-commerce platform builds its own branded interface — sellers see “Platform Pay” in the app, with their own branded card design — while every regulated activity (holding funds, processing transactions, AML/CFT screening) happens on the bank’s licensed infrastructure behind the scenes.
When a seller deposits earnings into their “Platform Pay” account, those funds sit in an account structure at the partner bank. If the account is structured as an actual deposit account in the seller’s name at the bank, SDIC coverage can apply up to the standard limit; if it’s structured as a pooled or omnibus account, the protection mechanics are different and sellers should check the platform’s terms to understand exactly how their funds are held.
Advantages of Banking-as-a-Service
- Faster time to market for embedded finance. Non-bank companies can launch banking-like features in months rather than the years it would take to obtain a banking licence.
- Lower capital and compliance burden for the non-bank partner. The heavy regulatory capital requirements sit with the licensed bank, not the consumer-facing brand.
- Lets banks monetise infrastructure at scale. Banks earn fee income from BaaS partnerships by servicing multiple non-bank clients through the same underlying systems.
- Enables deeply embedded, convenient products. Consumers get banking features exactly where they already spend time — inside a shopping app, gig platform, or payroll tool — rather than needing a separate banking relationship.
- Keeps regulatory accountability anchored to a licensed entity. Because the bank remains responsible for compliance, BaaS products still operate within Singapore’s regulatory perimeter rather than existing in a grey zone.
Risks and Limitations
- Consumer confusion over who actually holds the money. A well-designed BaaS product can make it unclear to the end user which licensed bank is actually responsible for their funds, complicating dispute resolution.
- SDIC coverage isn’t automatic. Deposit insurance protection depends on the specific account structure used, and pooled or omnibus arrangements may not give individual users the same protection as a standard personal deposit account.
- Non-bank brand failure creates operational risk. If the consumer-facing company (not the bank) fails financially or shuts down, users may face delays or friction accessing funds even though the underlying bank remains solvent.
- Complex accountability in disputes. When something goes wrong (a failed transaction, a fraud claim), it can be unclear to the consumer whether to pursue the non-bank brand’s customer service or the underlying bank’s complaints process.
- Regulatory evolution risk. As BaaS models mature, MAS may introduce more specific rules governing these arrangements, which could change how existing products operate or are marketed.
Banking-as-a-Service vs Open Banking
| Feature | Banking-as-a-Service (BaaS) | Open Banking (e.g. SGFinDex) |
|---|---|---|
| What it enables | Non-banks offering banking products via a bank partner’s licence | Secure sharing of financial data across institutions with consent |
| Who holds the funds | The licensed bank behind the BaaS arrangement | Funds stay with each customer’s own existing institutions |
| Consumer-facing result | A new branded account, card, or wallet product | A consolidated view of accounts across banks/CPF/etc. in one app |
| Singapore example type | Co-branded cards, embedded wallets in platforms | SGFinDex aggregating bank, CPF, and insurance data |
| Regulatory anchor | Banking Act, via the partner bank’s licence | MAS-led data-sharing initiative, consent-based |
Source: MAS API Exchange (APIX) initiative documentation, SGFinDex programme materials, 2026.
The Bottom Line
For Singapore consumers, understanding Banking-as-a-Service is important because many everyday apps that look and feel like standalone financial products are actually running on a licensed bank’s infrastructure behind the scenes. Knowing which bank ultimately holds your funds — and whether that structure genuinely qualifies for SDIC protection — is the key practical takeaway before relying heavily on any BaaS-powered account or card.