One-balance wallets block product roadmaps
Points, savings goals, and cash cannot share a coherent model without parallel ledgers.
05 · WalletMultipocket
Multipocket
by design.
Launch multipocket wallets — cash, points, savings, tickets, or operator-defined types — with typed units, conversion rules, and P2P flows behind your brand.
Built forRetail banks, neobanks, and super-apps that need wallet product velocity without rebuilding ledger plumbing
Model
Typed multipocket ledger movements
ICP
Banks · neobanks · super-apps
Controls
Conversion rules · SCA hooks · maker-checker overrides
What buyers are solving
Framed for Retail banks, neobanks, and super-apps that need wallet product velocity without rebuilding ledger plumbing — not generic payment pain.
P2P bolted onto core
Peer transfers become bespoke payment rails with unclear fees and arrival disclosure.
Conversion rules hidden in app code
Cross-type moves cannot be audited or disclosed consistently to customers and regulators.
How it works
- Define types
Operator configures pocket types and allowed units.
- Create pockets
Customers open pockets with labels and goals.
- Fund & move
Top-ups, transfers, and conversions per rules.
- Pay out
Withdrawals and merchant payouts with fees disclosed.
- Report
Statements and exports as you configure.
Customer wallet
Pockets
Core capabilities
Each capability names a concrete mechanism — not a marketing adjective.
Typed pockets
Each pocket has a type and unit semantics (money, points, tickets, savings) under one customer profile.
Multiple pockets per type
Customers can hold several pockets of the same type with distinct labels, goals, and icons.
Same-type transfers
Pocket → pocket movements post as ledger entries when units match — no silent FX.
Cross-type conversion rules
Operator-defined conversion with disclosure templates before the customer confirms.
P2P wallet ↔ wallet
QR or customer reference flows with fee and arrival-time disclosure on the initiating side.
Programme rules
Limits, eligibility, and pocket creation policies configured by the operator — not hard-coded in the mobile app.
SCA hooks
Strong customer authentication hooks for high-risk moves per scheme and local regulator guidance.
Assisted limit suggestions
Optional AI-assisted flags suggest velocity or limit adjustments for programme owners to approve — no silent limit changes.
Where this sits vs alternatives
Multipocket ledger semantics, conversion disclosure, and P2P rails are a product platform — not a weekend feature on core.
Many incumbents ship a single cash balance. Multipocket types are the default model here.
Global wallets often assume their payout network. Flagship Wallet is designed to sit with your bank rails, QR partners, and settlement exports.
Architecture and deployment
Customer apps call wallet APIs; pockets and movements are ledger-backed; payout and funding connect to your rails and settlement.
Customer surfacesYour branded app / web — white-label patterns
Wallet APIsPockets, transfers, conversions, P2P
LedgerImmutable movements between pockets
Rails & settlementFunding, payouts, exports to settle module
Deployment options
SaaS multi-tenant
Programme isolation per issuer in MENA-ready regions.
Dedicated tenant
Bank-grade isolation on dedicated or private-cloud tenancy.
Data residency options
Balances and PII reside in the programme region (EG / KSA / UAE options); cross-border classes listed in the DPA.
- HA/DR for ledger and API tiers with multi-AZ redundancy and programme RTO/RPO.
- Wallet signing keys follow HSM or managed KMS custody agreed in the enterprise DPA.
- White-label UX sits behind your brand; Flagship is the wallet control plane.
Integration experience
Typical integration is server-to-server wallet APIs plus your mobile UX. Examples are illustrative.
Illustrative example — not a live endpoint
Request
GET https://api.flagship.example/v1/wallets/wlt_9a2/balance Authorization: Bearer $FLAGSHIP_TOKEN
Response
{ "wallet_id": "wlt_9a2", "pockets": [ { "id": "pkt_cash", "type": "cash", "currency": "EGP", "available": "1500.00" }, { "id": "pkt_pts", "type": "points", "unit": "pts", "available": "4200" } ]
}SDKs & client libraries
Mobile and server SDKs (iOS, Android, Node) issued with your programmeREST wallet APIsWebhook events for movements
Integrations
SchemesQR railsCore APIs
Security and compliance
Balances are ledger-backed; high-risk moves use SCA hooks.
Ledger-backed movements
Pocket transfers create immutable audit entries — adjustments are new entries, not silent edits.
SCA for high-risk moves
Hooks follow scheme and local regulator guidance configured per programme.
Operator overrides
Maker-checker on overrides that move value or change programme rules.
Pricing orientation
Wallet programmes typically combine platform licence, active wallets, and transfer volume. Numbers on request.
Active wallets
Wallets with balance or activity in period.
Pocket types
How many type definitions and conversion matrices you run.
P2P / transfer volume
Monthly movements in scope.
Deployment
Shared vs dedicated tenancy.
Pricing follows programme design — not a public per-API sticker.
FAQ
Deal-killing objections, answered plainly.
Can two pockets share the same type?
Yes. Multiple pockets of the same type are supported with distinct labels.
How are FX or points conversions handled?
Cross-type conversions use operator-defined rules and customer disclosure templates.
Is the wallet white-label?
Yes. UX patterns are designed to sit behind your brand; Flagship provides the control plane and APIs.
Does this replace our core ledger?
It provides wallet pocket ledgers and exports. Your GL / core remains the bank of record as you design the integration.
Which QR rails are supported?
QR and instant-pay rails are enabled per market programme (for example Meeza QR where contracted) — confirm markets in a walkthrough.
Can AI change customer limits automatically?
No. Assisted suggestions go to programme owners for approval before limits change.
Related products
Design pockets before pixels
Bring the pocket types you want to launch. We will map ledger rules and sandbox access in a technical walkthrough.