Locanium
Use case

Onboard & pay out safely

Check bank details, phone and email before you activate an account or release a payout.

A user submits onboarding details
POST /v1/validate/ibanPOST /v1/validate/phonePOST /v1/validate/email
Verified before activation
See it

The flow in code

the flow · example
POST/v1/validate/iban200 OK
{
  "valid": true,
  "country_code": "DE",
  "bank": "Commerzbank",
  "bic": "COBADEFFXXX"
}
POST/v1/validate/phone200 OK
{
  "valid": true,
  "country_code": "US",
  "carrier": "Verizon",
  "line_type": "mobile"
}
POST/v1/validate/email200 OK
{
  "valid": true,
  "deliverable": true,
  "disposable": false,
  "free": false
}
Try every endpoint in the playground
One integration

Piece it together, or ship one flow

Before you activate an account or release a payout, the details have to be real: an IBAN that resolves to an actual bank, a phone that isn’t a throwaway, an email that will deliver. Skip the checks and bad accounts slip through — and a payout to a mistyped IBAN is money you don’t get back.

Piece it together yourself

  • Checks: Bank, phone, email — 3 vendors
  • IBAN: Regex that passes typos
  • Timing: Caught after activation
  • Billing: 3 invoices

One Locanium flow

  • Checks: 1 Locanium key
  • IBAN: Real validation + bank & BIC
  • Timing: Blocked before activation
  • Billing: One usage-based bill
Why Locanium

Why teams build it on Locanium

Three identity checks

Bank, phone and email verified in one flow before you activate.

Bank + BIC resolution

Validate the IBAN and return the bank, BIC and branch.

Catch bad details early

Block invalid accounts before a payout ever leaves.

One integration

IBAN, phone and email checks from a single key.

80+
Countries (IBAN)
3
Checks per flow
<40ms
Median response
FAQ

Questions developers ask

What does IBAN validation return?

Whether the IBAN is structurally valid and passes checksum, plus the resolved bank, BIC and branch — not just a regex pass.

Can it stop payouts to the wrong account?

Yes. Validate the IBAN before you release funds; a checksum-valid but wrong-bank detail is caught before money moves.

How many countries for IBAN?

80+ IBAN countries, with bank and BIC resolution where available.

Do you store applicant data?

No — checks run at request time, in-memory, with nothing retained. See the DPA and subprocessors for detail.

How fast is the full check?

Sub-40 ms median per endpoint. Run IBAN, phone and email in parallel and the whole gate adds about 40 ms.

Get started

One API for geolocation, currency and identity checks. Book a demo and get a sandbox key the same day.