Wallets are where money moves in our markets now. The Philippines passed an estimated 80 million registered e-wallet accounts in 2025, a threefold rise in five years, and real-time payments grew 24% year on year to 777 million transactions. Across Southeast Asia, digital wallets account for close to 40% of e-commerce payment value. 

To keep up, institutions must support a wider set of wallet-style accounts: 

• Retail accounts: Instant balance visibility for everyday spending 

• Merchant settlements: Immediate clearing and payouts for sellers 

• Partner networks: Real-time funds for local cash-in and cash-out points 

• Credit accounts: Dedicated accounts for instant credit drawdown and spending 

These account types require continuous processing, managing pooled and split customer funds, real-time reconciliation, payment rail integration, and continuous audit trails. 

But it’s hard to run a high-frequency transaction ledger beneath these features without overloading an installment-based core system. 

And building a digital wallet experience takes much more than a great front-end app. Behind it sit individual accounts and balances, individual and shared balances, real-time transactions, onboarding, reconciliation, auditability, payment connectivity, AML feeds and serious transaction throughput. All of that has to run somewhere. 

The trouble starts when you force a slow core to process thousands of instant account updates a second.  

Why wallet traffic overpowers legacy cores 

Lending is a low-volume, high-value pattern. A loan account might see a handful of transactions a month. A wallet-style account is the opposite:  

• Thousands of small transactions 

• Balances that have to be right in real time 

• Volume that arrives in bursts, like a payday or shopping festival 

When you try to force that fast payment traffic through an old system, everything gets messy very quickly: 

• Wrong balance totals: People see money that isn’t there or miss payments that just came in 

• Systems get stuck: The computer freezes because too many payments are trying to squeeze through at the exact same time 

• Daily checks fall behind: Your system can’t finish its end-of-day counting because digital money moves all night long 

No amount of fine-tuning turns a slow, loan-focused core into an instant transaction engine. 

Run your wallet accounts on an engine truly built for volume 

Want to launch wallets without overhauling your current core? Keep your primary core as the system of record and run high-volume accounts on a product engine built for real-time transactions. 

Powered by Oradian’s deposits and embedded finance capabilities, this model handles: 

• Flexible account types: Savings, current, individual, and combined balances 

• Instant balance updates: Live account views with zero delay 

• Easy accounting: Individual account activity stays on the engine, while the overall total flows back to your main core to keep your books balanced 

Oradian’s product engine processes 8,800 transactions per second and 12,000 journal entries per second, with sub-100ms API response times and 99.98% uptime. Every transaction posts as it happens and every balance is current. For example, FairMoney, a leading neobank, has more than 30 million accounts on a single deployment. 

Get your team on an engine they can flourish on  

Tapping into new wallet revenue requires team flexibility. With a product engine, your product team is able to configure account products including balance rules, fees, tiers, and limits. Your engineers connect them through stable, versioned APIsto the rails and wallets your customers use, InstaPay and PESONet in the Philippines, the local schemes elsewhere, and to your channels, across 750+ native endpoints. Real-time events feed transaction activity to your monitoring and AML systems as it happens, and Database Access gives your teams governed operational data for reconciliation and analytics without loading production. Not just that, but flows that are genuinely yours, like a merchant settlement rule, run as your own Custom Code, governed and auditable, with AI agents helping your team write them. 

The right product engine provides a measurable impact 

Here is the progress you will see when you move high-volume accounts off your main core: 

• Fewer complaints: Demonstrating customers trust balances  

• Faster settlements: Proving money moves in and out without delay 

• Zero peak-hour crashes: Showing your system holds up when traffic is at its worst 

• Shorter daily checks: Saving hours because real-time tracking removes month-end chasing 

The ground rules of adding a product engine  

With a product engine, you keep full control. Account products require sign-off, every change can be rolled back, and the general ledger stays as your single source of truth, even with millions of tiny payments flowing underneath. This can help you give auditors peace of mind. 

Roles stay distinct as well. You and your partners hold the regulated business, handling licensing, e-money compliance, and scheme relationships. Oradian delivers the underlying tech such as the real-time ledger, product setup, and open connections that bring your ecosystem together. 

Create and grow wallet revenue with Oradian’s product engine  

Your customers moved to real-time processing years ago. Wallet-style accounts are how your institution meets them there without asking a lending core to become something it isn’t, and without a core replacement standing between you and the product. Ready to launch wallets? Talk to our team at vanda.jirasek@oradian.com to get your product engine before the end of the year.