Move fiat across every bank — without building a single bank integration.
We build and run all your bank connections for you, so your engineers ship your product, not bank plumbing. One API for fiat on/off-ramps, treasury and reconciliation across your banks in APAC and worldwide — live in 6–8 weeks, not 6–10 months. You keep custody of your funds and credentials; we're a tech layer, not a bank.
Garbage in, garbage out.
Fiat is the hard part of crypto. Every bank speaks a different dialect — the same customer payment shows up in up to six formats and places. Specs run 300 pages, 40% out of date. Webhooks aren't 100% reliable. Building in-house is 6–10 months and a permanent maintenance tax. And if the money isn't reconciled in your bank account, the deposit didn't happen.
Why Acme
End-to-end delivery
We build it, run it, and manage the bank for you. You go live; we stay on the hook.
Live in 6–8 weeks
Not 6–10 months; ~80% less engineering time.
Maintenance is the moat
We absorb bank changes, format updates and the ISO 20022 / CBPR+ migration, at no extra cost.
One API, every bank
Connect once; add banks, currencies and regions without new integration work.
You keep custody
Non-regulated tech layer; we never touch your money; you keep funds and credentials.
Under your TMS/ERP
We power the layer behind Kyriba, GTreasury, FIS, SAP and your ledger. Not a rip-and-replace.
Named virtual accounts
Static, named virtual accounts for COBO and POBO. Each end-customer gets a dedicated account, so every fiat deposit auto-matches to the right user the moment it lands — no manual matching, no orphaned funds. Outbound payments carry the business's real name, not a generic label. Add a second bank for redundancy whenever you want; we test every bank/currency pair before go-live.
Use cases
Ripple
Ripple Treasury runs APAC fiat flows through Acme, the bank-connectivity layer between Ripple's banks and GTreasury across DBS, CIMB and more. Core live in weeks; expanded to balance inquiry and payments across entities and banks.
Libeara
The SC Ventures-founded fund-tokenisation platform runs its fiat and banking flows on Acme.
FAQ
Does Acme ever hold our fiat or our customers' deposits?
No. Acme is a non-regulated technology layer, not a bank, and never holds funds. Your fiat on/off-ramp accounts stay in your company's name at your own banks, and deposits move directly from your customers' banks into those accounts. Acme sends payment instructions, returns statuses and normalises the transaction data. Your bank credentials stay yours; Acme stores them PGP-encrypted, per customer and per bank, in AWS Secrets Manager in Singapore.
Is Acme a single point of failure for our fiat rails?
Acme is built so it shouldn't be, and you can add redundancy on top. Acme commits to 99.5% monthly uptime, caps its own maintenance at 3 hours a month with a week's notice, publishes live status at status.tryacme.com, and tests disaster recovery annually (3-hour recovery time). When a bank is under scheduled maintenance, the API returns a clear HTTP 503 so your platform can pause or reroute. You can also add a second bank for the same currency through the same API.
How do we match every fiat deposit to the right customer?
Give each customer their own named virtual account. Acme creates static virtual accounts through the API, and every credit to one carries that virtual account number, so each deposit maps to one user without manual matching. Deposits arrive as real-time webhooks where the bank supports them, and Acme deduplicates them against intraday and end-of-day statements, so a missed notification still appears from the statement. Virtual accounts support collecting and paying on behalf of your clients.
How long does it take to go live, compared with building it ourselves?
Typically 6–8 weeks, against 6–10 months to build in-house. Acme reads each bank's API or SFTP specification, builds the connection, manages the bank-side project and paperwork, and runs testing and live validation with you before go-live. Your engineers integrate once with Acme's REST API and can start in test mode, which doesn't touch live data or any bank. Bank-side onboarding varies by bank and can affect the timeline.
Which banks, currencies and digital assets can we connect?
Acme has 50+ integrations across 25 banks, led by APAC. Banks include DBS, OCBC, UOB, Standard Chartered, Citibank, HSBC, CIMB, Maybank, RHB, ANZ, Deutsche Bank and Zand, and currencies include SGD, USD, EUR, GBP, HKD, CNH and AUD, among others. For digital asset custody accounts, the API can look up balances and move assets such as BTC, ETH, XRP and USDC to and from external wallets. Rails and fields vary by bank, so we confirm coverage for your corridors.
What happens when a bank changes its spec or moves to ISO 20022?
Acme handles it as part of the service. We track each bank's changes, update the connection and keep our API versioned and backward compatible, so endpoints aren't removed without notice. Where a bank needs new data from you, such as fuller beneficiary names and addresses for the ISO 20022 (CBPR+) migration ahead of SWIFT's November 2026 deadline, we publish the field changes in our changelog in advance. We also shielded a client through Standard Chartered's core-banking upgrade.