Accounts API4

Balance Transfers API3

Balances API5

Capabilities API1

Captures API3

Chargebacks API3

Checkout Sessions API2

Client Links API1

Clients API2

Customers API7

Delayed Routing API3

Draft Transfers API4

Invoices API2

Mandates API4

Methods API7

OAuth API2

Onboarding API2

Organizations API3

Payment Links API6

Payments API6

Payouts API4

Permissions API2

Profiles API6

Refunds API5

Sales Invoices API5

Settlements API8

Subscriptions API7

Terminals API6

Transfers API2

Unmatched Credit Transfers API4

Verify Payee API1

postVerify Payee

Wallets API1

Webhook Events API1

Webhooks API6

Verify Payee API

Verify Payee

🚧 Beta feature

This feature is currently in beta testing, and the final specification may still change.

Perform a Verification of Payee (VoP) check. This allows you to verify the account holder name against the records held by the receiving bank before initiating a transfer.

The verification result indicates whether the provided name matches, closely matches, or does not match the name on file at the receiving bank. This helps prevent misdirected payments.

Simulating verification scenarios in test mode

In test mode, you can simulate various verification outcomes by adjusting the creditor name in the creditorBankAccount.accountHolderName property. This allows you to test all possible Verification of Payee results without needing special properties. The names are case insensitive.

Account holder name	Scenario	Verification result	Suggested name
John Close Match	Name closely matches the bank records	close-match	John Match
John No Match	Name does not match the bank records	no-match	—
John Unavailable	Verification is not available	not-available	—
Any other name	Default: name matches the bank records	match	—

post/v2/business-accounts/payee-verifications

Headers

idempotency-keystring

Example:123e4567-e89b-12d3-a456-426

A unique key to ensure idempotent requests. This key should be a UUID v4 string.

Request body

testmodeboolean nullable

Whether to create the entity in test mode or live mode.

Most API credentials are specifically created for either live mode or test mode, in which case this parameter must not be sent. For organization-level credentials such as OAuth access tokens, you can enable test mode by setting testmode to true.

Example request

{
  "creditorBankAccount": {
    "accountHolderName": "Jan Jansen",
    "format": "iban",
    "accountNumber": "NL02ABNA0123456789"
  }
}

Response

The verification result object.

Changes

Changed in 2 of the 92 revisions of this API.4

May 12, 2026ef4b5a97b56a2See the full diff
- ○
  the endpoint scheme security advancedAccessToken was added to the API
  api-security-added
- ○
  the endpoint scheme security organizationAccessToken was removed from the API
  api-security-removed
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Apr 30, 2026ec6fca28a7322See the full diff
- ○
  api tag Verify Payee API added
  api-tag-added
- ○
  api tag Verify Payees API removed
  api-tag-removed

Of the 92 revisions, 9 have no diff computed.

Full history