Cross-border and high-value payments, through one API.
Telegraphic transfers, book transfers and RTGS rails each come with their own bank formats, cut-offs and portals. Acme connects them for you, so treasury and ops teams send every high-value payment the same way.
Why run cross-border and RTGS through Acme
One request format
The same payment request for a telegraphic transfer, a book transfer or an RTGS payment.
Approvals before release
Turn on maker-checker so a second person approves each high-value payment.
Followed to a final status
We track each payment until the bank confirms it, and give you the bank's reason if it's rejected.
Format changes handled
Bank migrations such as ISO 20022 are absorbed by Acme, not your engineers.
Available in the following markets
Pick cross-border or high-value to see the local rails Acme connects in each market.
One request format, local or cross-border
A telegraphic transfer, a book transfer and an RTGS payment use the same request. Acme builds each bank's format and sends you a webhook when the bank answers.
FAQ
Can we use every rail listed?
The list shows the rails Acme has built in each market. Which ones you can use depends on where you hold accounts and what each bank approves for you. Tell us your banks and we'll confirm, or see Bank coverage for banks by market.
When should we use RTGS instead of a real-time rail?
RTGS rails such as MEPS+, RENTAS and CHATS are built for high-value payments that need same-day settlement. Real-time rails usually have lower per-payment limits. We'll help you choose per market.
Do you convert currency?
No. Acme sends your payment instruction to your bank, and any FX happens at your bank on your terms. Acme never holds your funds.
What happens when a bank moves to ISO 20022?
We handle the format change for you as part of keeping the connection live. Your API requests stay the same.