Skip to content

Take a test payment

Test merchants and projects in test mode, and where to find the test data of each connector.

Test every merchant setup before it processes live payments: the contract, the payment methods, 3-D Secure and the flows the merchant needs. You test on your own platform, with a project in test mode. No real money moves.

How test mode works

A project is in test mode while its status is active-testing:

  • Its orders get the is-test flag, in the portals and in the API.
  • The connectors send its payments to their test environments: the Silverflow sandbox, the Elavon test environment, the Rapyd sandbox, and so on.
  • For Silverflow, a project in active-testing is boarded in the sandbox, and the live project in production. See Silverflow merchant boarding.
  • The test credentials of your processors are set on your platform: a test project doesn't need the merchant's credentials.

To go live, you create the merchant's live project, in active-production: see Go live.

Take your first test payment

Test with the test project of the merchant you boarded: see Board a merchant.

Create an order

Log in to the Merchant portal, on your domain, with a user of the merchant, go to Payment links and create a link for a small amount.

Pay with test data

Open the payment link or the order's payment URL, and pay with the test card of your processor: see Test data per connector.

Check the result

In the Admin portal, go to Orders and open the order. Check its status, its transactions and the Webhook calls. A declined payment shows why: see Investigate a payment.

Test data per connector

Each connector has its own test cards, codes and amounts. They live on the connector page, so they stay with the connector they belong to.

ConnectorTest data
SilverflowTest cards, with the 3-D Secure code and CVC, and the amounts that trigger declines and other outcomes
BancontactTest Bancontact
ElavonTest data: the 3-D Secure code, test cards per outcome for Visa and Mastercard, and amounts per outcome for American Express
RapydTest cards
Shift4Test cards
IPGTest cards
Vipps MobilePayTest
SwishTest

The test data of the payment acceptance docs is for your merchants' developers. Send them there.

What to test

For every payment method the merchant uses, test at least:

  • A successful payment, and one that's declined.
  • A card payment with a 3-D Secure challenge, one that fails 3-D Secure, and one without a challenge, as far as the test data of your processor covers them.
  • The flows your merchants need: a refund, a capture of a pre-authorisation, a void, a recurring payment.
  • The webhook to the merchant: the project's webhook URL receives the status changes. Check Webhook Calls in the Admin portal.

When your tests pass, work through the Go-live checklist.