Payee verification request object

Learn how to send and respond to payee verification requests with Mambu Payments

AttributeDescription
objectAlways payee_verification_request.
idThe ID of the payee verification request.
statusThe status of the payee verification request. See Payee verification request lifecycle for more details.
failure_codeFailure code in case of failed request. One of:
  • business_error
  • technical_error
  • psp_technical_error
See Failure codes and status details for more details.
status_detailsStatus details in case of failed request. See Failure codes and status details for more details.
directionThe direction of the request. Can be outgoing or incoming.
schemeThe payee verification scheme used. Only vop is supported.
requestAn object containing key information about the request.
  • payee_identification_type
The type of identification used in the request. See Get supported identification types for a payee account for more information.
  • payee_identification
The identification of the payee.
  • party_account_number
The account number of the payee.
  • payee_additional_information
Additional information about the payee.
  • requesting_agent_bank_code
The BIC of the agent which sent the request.
  • responding_agent_bank_code
The BIC of the agent at which the request is aimed, i.e. the agent of the payee.
  • sent_identification
The payee identification actually sent to the responding PSP by Mambu Payments. It may be different from payee_identification in case the latter contains characters not accepter by the VOP scheme.
matching_resultThe result of the verification. Can be match, close_match, no_match, or impossible_match. Note that close_match is only possible when payee_identification_type = name.
payee_suggested_nameIn case of matching_result = close_match, name suggested as correct by the responding agent.
matching_detailsDetails of the request processing in case direction = incoming.
  • cleaned_identification
Payee identification after data cleaning (removing double spaces, honorific titles, etc.)
  • retrieved_identification
Payee identification used to compute the matching score, being the one from retrieved_identifications having the highest score when compared to received payee_identification.
null if all pairs result in a matching score of 0
  • retrieved_identifications
All identifications retrieved in your account database (in Mambu Payments (formerly Numeral) or in your systems), using payee_account_number as a search key.
  • internal_account_id
If your account database is held in Mambu Payments (formerly Numeral) using internal accounts, the ID of the internal account matching payee_account_number.
  • matching_score
The score, from 0 to 100, of the matching algorithm configured for your entity when executed with cleaned_identification and retrieved_identification.
scheme_dataAn object containing technical information about the request.
  • scheme_request_id
The unique ID of the request on the scheme. Different from id.
  • request_timestamp
The timestamp of the creation of the request.
  • response_timestamp
The timestamp of the answer to the request.
metadata

Additional data in JSON key:value format. See

Metadata

.

response_received_atThe UTC timestamp of the reception of the response to the request. Only available for outgoing requests.
created_atThe UTC timestamp of the creation of the VOP request.
{
    "created_at": "2025-02-12T01:34:24Z",
    "direction": "incoming",
    "failure_code": "null",
    "id": "c39d1eff-c5ed-4197-8f24-28a68bd0eee6",
    "idempotency_key": null,
    "matching_details": {
        "cleaned_identification": "Jean Dupont",
        "close_match_threshold": 80,
        "distance": "levenshtein",
        "internal_account_id": "e5cf0c31-c5fb-4e00-80fe-4338838d7493",
        "match_threshold": 95,
        "matching_score": 100,
        "retrieved_identification": "Jean Dupont"
    },
    "matching_result": "match",
    "metadata": {
        "payment_reference": "123-ABC"
    },
    "object": "payee_verification_request",
    "payee_suggested_name": null,
    "request": {
        "payee_account_number": "FR5012739000308682265435N36",
        "payee_additional_information": "Mr. Théo Dupont",
        "payee_identification": "Jean Dupont",
        "payee_identification_type": "name",
        "requesting_agent_bank_code": "SOMEBICXXX",
        "responding_agent_bank_code": "BANKITPPXXX",
        "sent_identification": null
    },
    "scheme": "vop",
    "scheme_data": {
        "request_timestamp": "2025-01-26T13:51:10Z",
        "response_timestamp": "2025-01-26T13:51:15Z",
        "scheme_request_id": "c3d79e5a-2058-4301-8b36-353cb9eb0ca5"
    },
    "status": "completed",
    "status_details": null
}
{
    "created_at": "2025-02-12T01:34:24Z",
    "direction": "outgoing",
    "failure_code": "null",
    "id": "c39d1eff-c5ed-4197-8f24-28a68bd0eee6",
    "idempotency_key": null,
    "matching_details": null,
    "matching_result": "match",
    "metadata": {
        "payment_reference": "123-ABC"
    },
    "object": "payee_verification_request",
    "payee_suggested_name": null,
    "request": {
        "payee_account_number": "FR5012739000308682265435N36",
        "payee_additional_information": "Mr. Théo Dupont",
        "payee_identification": "Jean Dupont",
        "payee_identification_type": "name",
        "requesting_agent_bank_code": "SOMEBICXXX",
        "responding_agent_bank_code": "BANKITPPXXX",
        "sent_identification": "Mr. Theo Dupont"
    },
    "scheme": "vop",
    "scheme_data": {
        "request_timestamp": "2025-01-26T13:51:10Z",
        "response_timestamp": "2025-01-26T13:51:15Z",
        "scheme_request_id": "c3d79e5a-2058-4301-8b36-353cb9eb0ca5"
    },
    "status": "completed",
    "status_details": null
}