curl --request POST \
--url https://api.next.orenda.finance/customers/{customerId}/beneficiaries/name-verification \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"identification": "12345612345678",
"ownerName": "Jordan Taylor",
"isCorporate": false
}
'{
"success": true,
"result": "MATCH",
"matchedName": "Jordan Taylor"
}Verification
Verify a payee name (CoP / VoP)
Verifies that a beneficiary’s name matches the name held by their bank before a payment is made. This single endpoint supports two schemes, distinguished by the request body:
- Confirmation of Payee (CoP, UK): send
identification(sort code + account number concatenated),ownerName, andisCorporate. - Verification of Payee (VoP, SEPA): send the structured
party,partyAccount(IBAN) andpartyAgent(BIC) objects.
The response reports whether the supplied name matches, partially matches, or does not match the account holder on record.
POST
/
customers
/
{customerId}
/
beneficiaries
/
name-verification
curl --request POST \
--url https://api.next.orenda.finance/customers/{customerId}/beneficiaries/name-verification \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"identification": "12345612345678",
"ownerName": "Jordan Taylor",
"isCorporate": false
}
'{
"success": true,
"result": "MATCH",
"matchedName": "Jordan Taylor"
}Authorizations
The back-office user's access token.
Path Parameters
The customer's ID.
Query Parameters
The program the customer/account belongs to. Required on every request.
Body
application/json
- Option 1
- Option 2
Confirmation of Payee (UK) request shape.
The payee's sort code and account number concatenated (6-digit sort code followed by the 8-digit account number).
Example:
"12345612345678"
The name the customer believes the account belongs to.
Example:
"Jordan Taylor"
Whether the payee account is a business (corporate) account rather than a personal one.
⌘I