Simulation tests for advanced credit and debit card payments

In the advanced credit and debit card fields, you can pass specific information to trigger simulated positive and negative test scenarios. You can handle these responses in your code to manage your customer’s experience.

Test with predefined verification responses

After your buyers submit an order, the request reaches a processor, such as Wells Fargo, to resolve the payment request. Processors return the address verification service (AVS), which compares the buyer's billing address against what the issuing bank has on file, and card verification value (CVV), the three- or four-digit number on the card, to provide insights into the transaction.

Enter CCREJECT- in the cardholder name field followed by the scenarios you want to test. You can simulate several scenarios:

  • INVALID
  • EXPIRED
  • REFUSED
  • BAD_DATA
  • ERROR
  • EXTERNALERROR
  • CALL
  • BANK_ERROR
  • CHALLENGE
  • XREFUSED

Note: Test values are case sensitive.

Here are some sample responses:

Test value Scenario Simulated error response
CCREJECT-EXPIRED Expired card "processor_response":{"avs_code":"G","cvv_code":"P","response_code":"5400"}
CCREJECT-INVALID Invalid card number "processor_response":{"avs_code":"G","cvv_code":"P","response_code":"1330"}
CCREJECT-REFUSED Do not honor card "processor_response":{"avs_code":"G","cvv_code":"P","response_code":"0500"}

Test with customized verification responses

Simulate unique responses based on the processor type and verification checks. There are four processors available:

Processor Test value
Consumer Portfolio Services (CPS) P
HSBC Bank USA H
Netgíró N
Wells Fargo W

Use one of two verification checks or a response code:

  • AVS – Any letters you choose
  • CVV – Any numbers you choose
  • Response code – Any digits you choose

Tip: Avoid combining various parameters into one request. A sample schema follows the CCREJECT-P-AVS_X syntax.

On this page