Account Numbers
Meridian Account Numbers lets institutions issue unique US routing and account number pairs at scale — one per customer, corridor, or use case — with automatic reconciliation, multi-rail inbound support, and real-time settlement.
The Problem
Most international institutions operating in the US rely on a single pooled account to receive dollar payments from many counterparties. Every inbound wire or ACH must be manually matched against a reference number — a process that breaks down as volume grows, corridors multiply, and payment descriptions become unreliable.
Meridian Account Numbers eliminates this by issuing a dedicated US account number for every counterparty or flow. Payments arrive pre-labeled. Reconciliation is automatic. And institutions can scale to thousands of sub-accounts without adding operational headcount.
How It Works
The institution requests one or more account numbers via the Meridian API, linking each to a counterparty, corridor, or purpose in their own system.
The assigned routing and account number is shared with the payer — an end customer, a partner institution, or an automated payment system.
Inbound payments arrive on ACH, Fedwire, RTP, or FedNow and are automatically matched to the correct virtual account in real time.
Credited funds are visible immediately on the sub-ledger and can be swept, held, or forwarded per the institution's configured rules.
Key Features
Issue unique US routing and account number pairs — one per customer or use case — with no pooled account reconciliation headaches.
Accept payments over ACH, Fedwire, RTP, and FedNow on a single account number — covering every major US payment rail in one integration.
Every inbound payment is automatically matched and posted to the correct sub-ledger entry — no manual file processing or batch reconciliation.
Receive structured payment data — sender, amount, rail, timestamp — the moment funds arrive, keeping your platform in sync without polling.
Configure automatic forwarding of inbound balances to a master account or downstream destination — on receipt or on a schedule.
AML screening, OFAC checks, and full audit trails on every inbound payment — issued under Meridian's regulatory framework from day one.
Technical Details
Compliance
Every inbound payment is screened against AML rules at the point of receipt, with automated holds and alerts for suspicious activity.
Real-time OFAC screening on all sender details before funds are credited, with configurable block and review workflows.
Each account number is linked to a verified counterparty record, giving institutions a complete audit trail from issuance to settlement.
Full immutable log of every account number issuance, payment receipt, sweep, and status change — available via API and dashboard export.
All account numbers are issued under Meridian's existing regulatory licenses, so institutions inherit compliant infrastructure without additional licensing burden.
Integration
A single REST API integration gives your institution the ability to provision dedicated US account numbers at scale — no US banking license, no correspondent relationship, no batch files.
Issue numbers individually or in bulk, configure sweep rules, and receive webhook events on every inbound payment — all from a single, well-documented API.
View API documentationcurl -X POST https://api.mnai.com/v1/account-numbers \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"label": "Customer USD receivables",
"counterparty_id": "cpty_abc123",
"rails": ["ach", "fedwire", "rtp", "fednow"],
"sweep": {
"enabled": true,
"destination": "acct_master_001",
"trigger": "on_receipt"
},
"metadata": {
"client_ref": "ACCT-USD-00291"
}
}'
Use Case
A regional bank in Southeast Asia receives USD payments on behalf of hundreds of corporate clients. Today, all inbound wires land in a single nostro account — requiring a back-office team to manually match every payment to the right client by memo line.
With Meridian Account Numbers, the bank issues a dedicated US account number to each corporate client. Inbound payments route directly to the correct sub-ledger. Reconciliation is automatic. The back-office team is freed from manual matching entirely.
<1s
Credit time on RTP & FedNow
10,000+
Accounts per institution
4 rails
ACH, Fedwire, RTP, FedNow
Frequently Asked Questions
A virtual account number is a unique, dedicated account identifier assigned to a specific counterparty or transaction flow. It routes inbound payments directly to the correct sub-ledger without requiring manual reconciliation, giving institutions full visibility at the transaction level.
Meridian Account Numbers support inbound payments via ACH, Fedwire, RTP, and FedNow. Each account number is a fully functional US bank account routing and account number pair, reachable on all major domestic rails.
Yes. Institutions can issue thousands of virtual account numbers through the Meridian API — one per customer, per corridor, or per use case. There is no practical limit, and each number is independently addressable and reconcilable.
Every inbound payment is tagged to its virtual account number and surfaced via webhook in real time. Institutions receive structured payment data — sender, amount, rail, timestamp — automatically matched to the correct account without manual intervention.
Yes. Meridian's account number infrastructure is designed for licensed financial institutions. All account numbers are issued under Meridian's regulatory framework, with full AML screening, KYC linkage, and audit trail support built in.
Yes. Institutions can configure automatic sweeps — forwarding inbound balances to a master account, a local currency wallet, or a third-party destination — on a schedule or on receipt. This supports zero-balance sub-account architectures.
Credit timing depends on the inbound rail. RTP and FedNow payments are credited in real time, 24/7/365. ACH credits settle T+1 standard or same-day. Fedwire credits are available same business day.
Schedule a conversation with our team. We'll walk you through the Account Numbers product, discuss your use case, and show you how quickly you can go live.