Testing Instructions

The Paysafe Test environment can be used to test websites or applications without running transactions through the Production (live) processing platform. Payment transactions processed in the Test environment (e.g., credit card payments) are not sent to the banking network, but through a simulator. Depending on the information provided with the transaction request, the simulator returns either a successful (approved) or failed (declined) response.

With the Paysafe Bank Account Validation API you can test the following:

  • Verify support for all the operation types that you require.
  • Review all common errors as well as errors that may occur for each operation, and ensure your application can handle them.
  • Verify the lengths and format for all attributes you send.

Testing Instructions

  1. Create a Bank Account Verification request using the values in the table below, depending on which response you want from the simulator.
  2. Request Example
    curl -X https://api.test.paysafe.com/bankaccountvalidator/v1/accounts/123456789/verifications \
      -u devcentre322:B-qa2-0-53625f86-302c021476f52bdc9deab7aea876bb28762e62f92fc6712d0214736abf501e9675e55940e83ef77f5c304edc7968 \
      -H 'Content-Type: application/json' 'X-Microservice-Mode: simulation' \
      -d '{
    	"merchantRefNum": "123simulation",
    	"accountTypes": [
    		"CHEQUING",
    		"SAVING"
    	],
    	"currencyCodes": [
    		"CAD",
    		"USD"
    	],
    	"returnLinks": [{
    		"rel": "default",
    		"href": "https://www.mysite.com/"
    	}],
    
    	"bankScheme": "EFT",
    	"profile": {
    		"firstName": "richard",
    		"middleName": "william",
    		"lastName": "cohen",
    		"locale": "en_CA"
    	}
    }'
  3. Include the following header:
  4. X-Microservice-Mode:SIMULATION

  5. Post it to the following endpoint:
  6. https://api.test.paysafe.com/bankaccountvalidator/v1/accounts/<account_id>/verifications

  7. Copy the redirect link returned in the href to a browser and select the Flinks Capital bank for testing purposes.
  8. Response Example
    {
    	"id": "818506be-7645-407a-9120-b389f79f2ba5",
    	"sessionId": "Mjg2MDhmYTEtYTVjZi00MDg5LWE5MjEtOGU1MzE3OWU2NjUz",
    	"links": [{
    		"rel": "redirect_bank_validation",
    		"href": "https://api.test.paysafe.com/bankaccountvalidator/v1/redirect?sessionId=Mjg2MDhmYTEtYTVjZi00MDg5LWE5MjEtOGU1MzE3OWU2NjUz"
    	}],
    	"status": "INITIATED",
    	"merchantRefNum": "123simulation",
    	"accountTypes": [
    		"CHEQUING",
    		"SAVING"
    	],
    	"currencyCodes": [
    		"CAD",
    		"USD"
    	],
    	"bankScheme": "EFT",
    	"profile": {
    		"firstName": "richard",
    		"middleName": "william",
    		"lastName": "cohen",
    		"locale": "en_CA"
    	},
    	"returnLinks": [{
    		"rel": "default",
    		"href": "https://www.mysite.com/"
    	}]
    }
  9. Follow the instructions at the bottom of the screen for entering the correct credentials.
  10. On the resulting page for challenge questions, follow the instructions at the bottom of the screen for entering the correct answer.
  11. If the correct name and online banking credentials are entered, the user will be presented with the associated EFT/ACH-eligible accounts to select from for payment.
  12. Submit or Cancel the selected account.
  13. Do a Verification Lookup GET request to retrieve the bank account details and the single-use paymentToken associated with the selected bank account

Simulator Test Values

  • The test values are case sensitive.
  • The value for middleName must be provided exactly as found in the table below.
  • You can modify the firstName and lastname slightly to see the results of the name-matching algorithm used.
Field Value Results

firstName + middleName + lastName

diff + ramiro + account

Simulator response contains 10 accounts:

  • Chequing CAD
  • Chequing US
  • CreditCard
  • RRSP
  • LineOfCredit
  • LoanPersonal
  • Savings CAD
  • Chequing CAD (TransitNumber as null)
  • Saving CAD
  • Chequing INR
richard + william + cohen

Simulator response contains 3 accounts:

  • Chequing CAD
  • Chequing US
  • Saving CAD
françois + jacob + dubé-alzner

Simulator response contains 4 accounts:

  • Chequing CAD
  • Chequing US
  • CreditCard
  • RRSP
peter + brandon + parker

Simulator response contains 2 accounts:

  • Chequing CAD
  • Chequing US
account_id Your Test account ID Use the account number you received from Paysafe when you applied for the Test account.

Applying for a Test Account

You can apply for a Test account by clicking the SIGN UP button.

Your Test account will provide you with access to a Test version of the Paysafe Merchant Back Office, where you can view the status of your Test transactions. Once logged in to the Back Office you should also retrieve your Account Number (choose Accounts and copy it from the Account column) and your API Key User name and Password (choose Settings > API Key); the password is also available Base64 encoded.

Test API Endpoint

The API endpoint to use for Test transactions is:

https://api.test.paysafe.com

For example:

https://api.test.paysafe.com/bankaccountvalidator/v1/accounts/account_id/verifications

Test and Production Accounts

Test accounts enable you to process API transactions that mirror the functionality on the Production environment. Once you are satisfied with your integration to the Test environment, you will need to repeat any configuration changes made to your Test account on the Production account. Keep a record of any changes requested and carried out.

You will need to use different API endpoints and authentication credentials to connect to the Paysafe Production environment.

For details see Going Live.

Did you find this page useful?