Create a Bank Account Verification
A bank account verification request allows merchants to send initiate the bank account verification request by sending some information about the customer to Paysafe, along with a few other parameters. The response to the POST request will contain a redirect URL by which the customer will be able to select a bank and verify that they, in fact, own the bank account(s).
See our full API documentation for a complete description of the parameters required for the Payment request.
curl -X https://api.test.paysafe.com/bankaccountvalidator/v1/accounts/123456789/verifications \
-u devcentre322:B-qa2-0-53625f86-302c021476f52bdc9deab7aea876bb28762e62f92fc6712d0214736abf501e9675e55940e83ef77f5c304edc7968 \
-H 'Content-Type: application/json' \
Prior to trying the example, you should:
- Replace the account number (123456789) in the URL with the test account number you received.
- Replace the API key (after the -u) with the API key you have received.
- Provide a unique merchant reference number for each transaction.
The request contains the following parameters:
|Yes||This is the merchant reference number created by the merchant and submitted as part of the request. A unique merchant reference number must be provided for each transaction.|
|profile||object||Yes||This is some profile information about the customer.|
|Yes||This is the customer's first name.|
|No||This is the customer's middle name.|
|Yes||This is the customer's last name.|
This indicates the language of the user interface.Possible values are:
This is the list of bank account types that will be presented. Possible values are:
If this parameter is not included, the default response will return EFT-eligible saving/chequing accounts.
This the currency of the bank accounts that will be presented. Possible values are:
If this parameter is not included, the default response will return CAD/USD currency accounts.
|returnLinks||array of objects||Yes|| |
These are URL endpoints to which to redirect the customer. You can customize the return URL based on the transaction status. The default value is mandatory.
This is the link type, allowing different endpoints to be targeted depending on the end state of the transaction. The link relation describes how this link relates to the previous call. Possible values are:
|href||string||Yes||The actual URL to which the customer will be redirected.|
This is the bank scheme for which the merchant wants to validate the account. Possible values are:
The response parameters not contained in the request are described below:
|Unique ID for this bank account verification operation. This ID can be used to look up the verification later.|
|Unique session ID for this operation. This session ID is used in the redirect URL for the customer to validate their bank account.|
The status of the request. Possible values are:
|links||object||This is an array of links related to the resource.|
This is the link to the endpoint at the end of the transaction. Possible values are:
|href||string||The actual URL to which the customer will be redirected.|