VoP Response

BaaS Partners must be able to consume an object in the Initiate Payment API response body called: payeeVerification

This object contains all relevant VoP response data and must be displayed to your BaaS Clients via your platform’s front-end (e.g., app or web).

As a BaaS Partner, you must:

1. Display the VoP response to your BaaS Clients via front-end only when the Initiate Payment API response contains: paymentRail="SEPA_SCT" or "SEPA_SCT_INST"
2. For all other paymentRail values (i.e., INTERNAL and SWIFT), VoP is not mandatory. Therefore you will receive object payeeVerification=null and there is nothing to be displayed as the VoP response to the BaaS client via the platform’s front-end.

Example of Initiate Payment API response body, when paymentRail="SEPA_SCT"

{
  "paymentOrderNo": "s-70752374481170997670",
  "paymentRail": "SEPA_SCT",
  "transactionStatus": "RCVD",
  "transactionFeeIndicator": true,
  "transactionFees": {
    "amount": "5.00",
    "currency": "EUR"
  },
  "payeeVerification":{
    "matchType": "MTCH"  
  },
  "_links": {
    "self": {
      "href": "https://api-stage.connectpay.com/ob/payments/s-70752374481170997670"
    },
    "status": {
      "href": "https://api-stage.connectpay.com/ob/payments/s-70752374481170997670/status"
    }
  }
}

Example of Initiate Payment API response body, when paymentRail="INTERNAL"

{
  "paymentOrderNo": "s-70752374481170997670",
  "paymentRail": "INTERNAL",
  "transactionStatus": "RCVD",
  "transactionFeeIndicator": true,
  "transactionFees": {
    "amount": "5.00",
    "currency": "EUR"
  },
  "payeeVerification": null,
  "_links": {
    "self": {
      "href": "https://api-stage.connectpay.com/ob/payments/s-70752374481170997670"
    },
    "status": {
      "href": "https://api-stage.connectpay.com/ob/payments/s-70752374481170997670/status"
    }
  }
}

The response body will include the payeeVerification object, which indicates the result of the name–IBAN check. This value must be used to determine how the VoP response is presented to the BaaS Client via your platform’s front-end channels (e.g., app or web).

Payee Verification valuesDescription
"payeeVerification":{ "matchType": "MTCH" },Match – the provided payee name matches perfectly with the account holder.
"payeeVerification":{ "matchType": "CMTC" "matchedName": "<suggested name>"" },Close match – minor discrepancies found (e.g., spelling differences) and includes a suggested correct name: matchedName: "<suggested name>"
"payeeVerification":{ "matchType": "NMTC" },No match – provided name does not match the account holder’s name.
"payeeVerification":{ "matchType": "NOAP" },Verification of payee is not possible – the check cannot be completed due to technical issues, unsupported IBAN, system unavailability, etc.
"payeeVerification": nullVerification of payee is not applicable and there is nothing to be displayed as the VoP response to the BaaS client via the platform’s front-end.

As a BaaS Partner, you must:

1. Display the VoP response (based on the payeeVerification.matchType) to the BaaS Client (sender) before they authorize the payment.
2. Use your platform’s front-end channels (e.g., mobile app, web application) to present this information.
3. Allow the BaaS Client to decide whether to proceed with or cancel the payment based on the VoP response.

If the BaaS Client chooses to proceed with the payment despite receiving a VoP response with either of the following match types:

"matchType": "NMTC" → No Match

"matchType": "NOAP" → Verification Not Possible

Then, in the event of a fraudulent transaction, neither ConnectPay nor the BaaS Partner/Platform will be liable for a refund.

Note! This liability rule is defined under the EU Instant Payments Regulation (IPR) and applies to all payment service providers and platforms in the Eurozone.

Scroll to Top