Testing your ProcessOut integration

Testing your ProcessOut integration is crucial to make sure everything works as intended before pushing your code into production. ProcessOut provides you with a few tools you can use to quickly check everything.

Testing environment

A testing environment is available for developers who want to test their integration of ProcessOut. We strongly advise you to use our testing environment when implementing any of our products.

Most of the ProcessOut objects can be created in the production or test environments. Objects created in one environment will not be available in the other. Objects created in the testing environment will have the attribute sandbox set to true.

To enable the testing environment, simply prepend your project ID with test- when instanciating the ProcessOut clients and use your sandbox private key, like so:

curl -X GET https://api.processout.com/ \
    -u test-proj_gAO1Uu0ysZJvDuUpOGPkUBeE3pGalk3x:key_sandbox_mah31RDFqcDxmaS7MvhDbJfDJvjtsFTB
var ProcessOut = require("processout");
var client = new ProcessOut(

import processout
client = processout.ProcessOut(

require "processout"
client = ProcessOut::Client.new(

$client = new \ProcessOut\ProcessOut(

import "gopkg.in/processout.v4"
client := processout.New(

Warning: Remember to remove the test prefix when switching to production.

Test cards

When using the test environment, test cards can be used to simulate real-world cards. We provide you with a handy set of test cards in different brands, as well as special cards which will have a special effect when used during checkout. This is meant to help you test special test cases easily.

Please note that any real-world card will not work in the test environment. Also, the expiry date and CVC code of the cards will not be checked.

Cards that will result in a successful payment:
4242 4242 4242 4242
5555 5555 5555 4444
3782 82246 310005
American Express
3012 3456 7890 19
Diners Club
3530 1113 3330 0000
6011 1111 1111 1117
Cards with 3-D Secure specific behaviour:
4000 0000 0000 0101
3-D Secure supported and required on the card
4000 0000 0000 0119
3-D Secure not supported on the card
Cards that will have a special behaviour:
4000 0000 0000 0002
The credit card will be denied
4000 0000 0000 0010
The authorization on the card will be successful, but any capture will fail
4000 0000 0000 0028
The CVC check will fail
4000 0000 0000 0036
The AVS check will fail
4000 0000 0000 0044
The CVC and AVS checks will both fail
4000 0000 0000 0069
The payment will be successful, but a chargeback will be initiated as soon as the payment makes it through