Now self-serveAccess PayOS data to make better payment decisions, no sales call needed.Start building →
‹Bank Data

Verify bank accounts anywhere, with one call.

Add a country to the account and PayOS routes it to global verification automatically. Same endpoint, same answer: GREEN, ORANGE or RED.

POST /bank/accounts/verifyWaiting for input
Country
🇩🇪DE
IBAN
 ✓
Account holder
 ✓
⇄Routed to global verification · IBAN · Germany
trafficSignal: "…"
Waiting for result

International bank verification in a single API.

The same endpoint verifies US and international accounts. Include the account’s country, and PayOS routes it to global verification.

The request
{
"account": {
"accountNumber": "DE89370400440532013000",
"accountNumberType": "IBAN",
"postalAddress": { "country": "DE" }
},
"entity": { "individual": { "firstName": "Hans", "lastName": "Schmidt" } }
}
⇄The account’s country is what routes the request. Nothing else changes.
Each country, its own format
Send what the country uses. PayOS handles the rest.
🇺🇸
United States
Routing + account
ABA
🇩🇪
Germany
IBAN
IBAN
🇮🇪
Ireland
IBAN + BIC
BIC
🇬🇧
United Kingdom
Sort code + account
SORT_CODE
🇮🇳
India
IFSC + account
IFSC
🇦🇺
Australia
BSB + account
BSB
🇫🇷🇪🇸🇮🇹🇳🇱🇧🇪🇵🇹🇦🇹🇨🇭🇸🇪🇳🇴🇩🇰🇫🇮🇵🇱🇨🇿🇬🇷🇨🇦🇲🇽🇧🇷🇸🇬🇯🇵🇭🇰🇳🇿🇦🇪🇿🇦🇱🇹🇱🇺🇷🇴🇭🇺🇫🇷🇪🇸🇮🇹🇳🇱🇧🇪🇵🇹🇦🇹🇨🇭🇸🇪🇳🇴🇩🇰🇫🇮🇵🇱🇨🇿🇬🇷🇨🇦🇲🇽🇧🇷🇸🇬🇯🇵🇭🇰🇳🇿🇦🇪🇿🇦🇱🇹🇱🇺🇷🇴🇭🇺
And many more markets
Each in its local format. Postal codes, regions and provinces follow local conventions too.

Verification results in every market.

Global verification returns the same traffic signal as US verification, with the reason code behind it.

"GREEN"
Pay with confidence
POS_1000Account active and valid
POS_6100Ownership match
→ Release the payment
"ORANGE"
Take a second look
POS_6150Name only partly matches
POS_3010Account located, status unknown
→ Step up or confirm the name
"RED"
Don’t send
POS_2000Account closed
POS_4000Invalid account format
→ Stop before money leaves

Use cases for global bank verification.

Each card is a problem global verification prevents.

!
Payout · €4,200Sent
BeneficiaryNot the owner
Recall takes weeks
01
A cross-border payout lands in the wrong account
✓Verify the IBAN and the owner before you send.
DE893704004405320I3000
not a valid IBAN
02
One wrong character in a 22-character IBAN
✓Catch format and checksum errors at entry.
GivenSean Murphy
Bank recordSeán Ó Murchú
Partial match · review
03
Names don’t line up across languages
✓A partial match returns ORANGE with POS_6150, not a hard fail.
Lives in🇺🇸 United States
Account in🇮🇪 Ireland
Verified, not rejected
04
A customer at home in one country, banking in another
✓Cross-border holders are processed normally.
🇩🇪 Bank API A
🇬🇧 Bank API B
🇮🇳 Bank API C
POST /bank/accounts/verify
05
A separate integration for every market
✓One endpoint, routed by the account’s country.
!
New bank details received
OldGB •••• 4412
NewLT •••• 0931
06
An overseas supplier “changes banks”
✓Re-verify the new account before the next invoice.

Global bank coverage.

Verify accounts in the markets you pay into, through the same call you use at home.

Decide with confidence.

One integration
US and international accounts, same endpoint.
Fewer misdirected payouts
Owner confirmed before money crosses borders.
Fewer returns and recalls
Bad IBANs caught before submission.
Safer supplier payments
New overseas bank details verified first.