Online Payments

Overview

The Service Provider Simulator works like a processor and allows you to test your transactions in a sandbox environment based on your linked Payment Provider Contract. See here how to get started.

The Simulator is designed to assist with integration testing and troubleshooting. If the simulator processor is not available to you, please contact your Verifone administrator. The Simulator can be configured without any need to provide your acquiring merchant ID or any other credentials. 

Availability

Available to all merchants who want to test in a sandbox environment.

Service Provider Simulator

Authorize and settle transactions

Once your Payment Provider Contract (PPC) is set up in the sandbox, you can start testing. 

When testing using a PPC configured with the simulator, you may also mock the settlement process. If you have requested to capture a transaction, either by using the capture_now flag during the authorisation or the capture API, the transaction will be updated automatically to Settled status after 60 mins.

In the Production environment, the settlement will take place according to a fixed scheduled time per acquirer (usually this happens at the end of the day, but read the Acquirer documentation for more details). However, Verifone system is set up to have the settlement take place 60 mins after authorization. Having a transaction in Settled status is a prerequisite to be able to initiate a refund. 

Combine transaction tests with 3-D Secure

To combine transactions with the 3-D Secure flow, simply use the cards listed for 3DS 1.0 and for 3DS 2.0 to trigger the relevant behavior. 

Trigger specific error responses

Generally, all transactions initiated against the simulator would be approved with a code 0000. However, in production, you may encounter failed transactions.

There are two ways to trigger unhappy flows:

• you can use a specific value for the amount and, in this case, when the amount ends in the values below, a relevant error code will be invoked as described in the table.
• you can use the merchant_reference parameters. When the merchant_reference is equal to the values below, a relevant error code will be invoked as described in the table.

Trigger a specific CVV result

Initiating card transactions can return several different responses for the CVV check. Those scenarios can be tested by sending an appropriate value for the CVV.  The cvv_result values can be invoked as described in the table below. 

Test in production 

After your account was set up and you received all your credentials to be used in the Production environment, you are ready to start testing!