Visa

• Overview
• Countries & currencies
• Integration
• Process flows
• Testing
• Additional information

Testing

• Using test card generator
• Testing scenarios

Test card generator

You can use our Test card generator and API Reference to create payments and receive responses based on your selected test scenarios. You can use our API Explorer to test your integration. Testing is available only in pre-production. To activate our advanced Card-based Payment Testing Simulator on your merchant ID, contact our boarding team. 

To validate your integration, you can select the card payment product you want to test as well as the outcome of the test case you want to validate. Based on your selection, you will receive a card number and additional details you can put in your API request. 

Follow these simple steps to start testing:

1. Select payment product for which you want to generate test data. Test data is only available for payment products configured with your merchant ID.
2. Select issuing country. This shows the card issuer's country where the account is registered, which determines 3D Secure usage. If your country isn't listed, select one from the same region (in brackets) for similar payment processing behavior.

1. Specify card type. Card types are distinguished based on their features and usage. These types determine the card's functionality, such as the processing flow or associated benefits. System will automatically choose the default value if no selection is made.
2. Select co-badged scenario if required. Co-badged cards feature several payment brands, allowing acceptance through the networks of each brand and increasing versatility.

• This field will be enabled or disabled for selection depending on the payment product chosen.

1. Choose a 3D Secure & Strong Customer Authentication (SCA) testing scenario. This enhances online card transaction security with additional verification steps:

• Authentication type: Indicates the 3D Secure process, where the issuer may request additional data from the consumer during transactions.
• Authentication result: Shows the issuer's authentication level, affecting liability and next steps.
• Exemption result: Indicates if a transaction can skip extra authentication steps in 3D Secure based on its risk assessment.

1. Select fraud management testing scenario:

• CVV result: Response from the card issuer when the Card Verification Value (CVV) is submitted during the authorization.
• AVS result: Address Verification Service (AVS) compares the cardholder's billing address with the issuer. It's mainly used for cards from the US, Canada, UK, and France.
• Fraud service result: Our tool evaluates transactions for risk and flags suspicious activities, with results displayed in the API response.
• System will automatically choose the default value if no selection is made.

1. Choose authorization result to test if the card issuer approves or declines your transaction request. The result will be shown in the API response:

• Successful: Transaction is approved and authorized.
• Unsuccessful: Transaction is declined or rejected.
• System will automatically choose "Successful" as default value if no selection is made.

1. Select authorization scenario for unsuccessful results. These are provided when the issuing bank declines an authorization request.

• This field will be available for selection when authorization result has been chosen as "Unsuccessful".
• System will automatically choose the default value if no selection is made.

1. Specify refund scenario by selecting how the API should respond when processing refunds for this test card:

• This field will be available for selection when authorization result is "Successful".
• System will automatically choose "Successful" as default value if no selection is made.

1. Generate test card. Click on "Generate" button to generate test card and other test data based on your selected testing scenario. To generate new test with new properties, you can reset your selection. Use this test card and other generated test data in your hosted checkouts or S2S API request towards Worldline and receive the response for the chosen scenario.
2. Reset for new scenario. If you want to generate a new test scenario, click on the "Reset" button and choose new test card and data corresponding to a new test scenario.

Test scenarios

Positives

Below are the positive test case input definitions with the expected results in the last 4 columns. Positive in this context means that the payments get an authorization. Be aware that the Fraud service can have influence on the final payment status.

Negatives

The negative cases are simulating transactions that do not get an authorization. There are lots of different reasons why a transaction gets declined. More info what the reasons are, are found in the event code description.

Currencies

To be able to test every single currency as listed in the currency table, please use following details.

Fraud Services

Fraud services are by default enabled. The field CITY is controlling the outcome of the fraud check:

For the 525 status a formal decision is required to accept the payment or decline it. The API processchallenged is needed to accept the payment; the status will change to 800. When the payment needs to be declined the CancelPayment will set the status to 99999 (cancelled).

It is also possible to turn off the fraud services per transaction by adding skipFraudService: True to the request. There will be no fraud result in the responses.

3D secure

On payment product id 117 (maestro) 3d secure is enabled as all Maestro transaction are mandated to be processed with 3D secure.

AVS

Address verification is enabled on all cards that support it. Different cases give different AVS result. In case the card type isn’t supporting AVS, the result will always be 0.

Delayed settlement

By default all transaction are set to Delayed settlement, except for the product that don’t support it. In Sale mode, payment will lead to status 800.
In Auth/Capture mode, a payment will lead to status 600, which subsequently requires to do a ApprovePayment to make the status go to 800.

Card verification

Also known as 0$ authorization. This type of transaction is triggered with an amount of 0 and will only return a validated response resulting in a status of 300 and only works on a recurring model.

Refunding

Transactions are not refundable on status Completed with status ID 800, as for that a separate process is scheduled to have the payment end up on a refundable status. Please wait for 1 hour for all your test transactions at status Completed with status ID 800 to be processed like this and set to be ready for refunds.

3D secure handling

For the handling of transaction with 3D secure a redirect takes place for the consumer. In the Sandbox it will not show a login screen but a functional HTML form that needs to post the 3D secure validation to the payment platform. Please use that process to simulate the authentication process. The post action triggers the right action to be able to finish the payment.

The redirect behavior back and forward are as it would be in real production systems.

Sample of the form: