curl --request POST \
--url https://api.next.orenda.finance/v1/beneficiaries/verify \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"beneficiary": {
"name": "Jordan Taylor"
},
"account": {
"type": "uk",
"sortCode": "123456",
"accountNumber": "12345678"
}
}
'{
"success": true,
"data": {
"match": true,
"name": "Jordan Taylor",
"reasonCode": "MTCH",
"reasonCodeDescription": "Name matches the account holder."
}
}Verification
Verify a payee name (CoP / VoP)
Verifies that a payee’s name matches the name held by their bank before a payment is made. One endpoint covers both schemes — it picks the scheme from the account you send:
- Confirmation of Payee (CoP, UK): send
accountNumberas 14 digits (6-digit sort code + 8-digit account number), or the discriminated form{ "type": "uk", "sortCode": "…", "accountNumber": "…" }. - Verification of Payee (VoP, SEPA): send
iban, or{ "type": "iban", "iban": "…" }.
Send exactly one of iban or accountNumber.
POST
/
v1
/
beneficiaries
/
verify
curl --request POST \
--url https://api.next.orenda.finance/v1/beneficiaries/verify \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"beneficiary": {
"name": "Jordan Taylor"
},
"account": {
"type": "uk",
"sortCode": "123456",
"accountNumber": "12345678"
}
}
'{
"success": true,
"data": {
"match": true,
"name": "Jordan Taylor",
"reasonCode": "MTCH",
"reasonCodeDescription": "Name matches the account holder."
}
}Authorizations
The back-office user's id_token — the ID token, not the access_token. The API rejects access tokens.
Query Parameters
The program the customer/account belongs to. Required on every request.
Body
application/json
⌘I