Eleven currencies, one integration.
Each account is issued in the customer's local currency and uses the rail people already use there.
Some currencies need identity checks before the account is issued, and pound accounts are for business customers. Peso and real accounts are switched on per merchant. Our API lists what each currency needs, so your form never goes out of date.
Permanent for regulars, one-time for invoices.
Which type is available depends on the currency. You see that before you issue an account.
Dedicated account
A permanent account number that belongs to one customer.
One-time account
A temporary account for a single payment, with an expected amount and an expiry.
From customer to payment in four steps.
Create a customer
Add an individual or a business. An email and a name are enough to start; add identity details when a currency needs them.
Issue an account
Pick the currency and the type. You get the account details back to show your customer, or a verification link if the provider needs one first.
Your customer pays
They send a bank transfer to the account, the same way they pay any other bank account.
You get a signed webhook
We confirm the payment with the bank, match it to the customer, and notify your system. Funds settle to your balance.
Wrong amounts and third-party payments are handled, not ignored.
Paid too little or too much
On one-time accounts we compare what arrived with what you asked for. A difference is flagged and reviewed before it settles, and you get a manual review webhook with the expected and received amounts.
Paid by someone else
For dollar, euro and pound accounts, a payment from a sender who is not your customer can be held for review. The rule depends on your risk tier, so low and medium risk merchants are not slowed down.
Confirmed with the bank
We never credit from a webhook alone. Every payment is checked against the provider before it counts, so a spoofed notification cannot create a payment.
One request. The same shape in every currency.
Account details come back in one normalized object, whether the rail is a US routing number, an IBAN, a sort code or a local account number, so adding a country never changes your code.
Every webhook is signed, so you can verify it came from us.