Back to neotek ↗Get Sandbox Access

We’ve created a sandbox session for you — no signup needed. Explore freely. All data is mocked. No real bank connection is made.

IBAN Verification

Confirm an IBAN belongs to the person or company you think it does.

In production, this replaces: cancelled-cheque uploads, bank letters, and failed transfers to mistyped IBANs.

  1. Check (current step)
  2. Result

Step 1 — Check an IBAN

IBAN Verification is a Premium product: no accounts link, no consent journey. It answers whether an IBAN belongs to the identity you name. Nothing is sent until you press verify.

Request

The reference documents three endpoints and prints an envelope for each, so all three are offered here.

POITypeNAT
POINum1523698745
IBANSA1080000012345678901002

These are the sandbox values the reference states resolve in the test environment. Note the async leg names the field POINumber where the synchronous ones use POINum.

GET /iban/v1/verify?POIType=NAT&POINum=1523698745&IBAN=SA1080000012345678901002

REQUEST INSPECTOR

No requests yet

Start a demo flow — each simulated API call appears here as it fires.

Step 2 · Read the reference

IBAN Verification documentation

Endpoints, auth, payloads, and error handling for production.

Open the docs

Step 3 · Build for real

Start your first sandbox call

Create a sandbox app, copy your client credentials, and call IBAN Verification with real bank data.

Start your first sandbox call