IgnitionDeck Documentation

Payment Gateway Testing

The following are some brief notes on how to approach testing the various payment gateways that integrate with IgnitionDeck Commerce (IDC).

NOTE: Because testing some gateways requires setting up a test or “sandbox’ account, and because this process can be complicated (depending on the gateway), sometimes it’s faster and easier to simply create test products or crowdfunding levels that only cost a small amount of money, and test using actual transactions, if doing so is a viable option for your purposes.

Click on a payment gateway name to jump to the notes for that gateway:

PayPal (Standard)

When using PayPal as a gateway, the typical method for testing is to set up a “Sandbox” account for both buyer and seller. Insert these test credentials (instead of your real ones) in the IDC > Gateways > PayPal menu while your platform is in test mode.

Please refer to PayPal’s documentation page called Creating Sandbox Test Accounts


Stripe provides each of its users with a test Stripe Publishable Key and a test Stripe Secret Key. Enter these in their respective fields in IDC > Gateways > Stripe. Then enable test mode at the top of your Gateways screen, and IDC will use the test credentials instead of the live ones. In addition, Stripe provides a number of test test credit card numbers that can be used for testing purposes.



When using Authorize.Net as a gateway, the typical method for testing is to set up a “Sandbox” account. This test account is used to create a test API Login ID and test Transaction Key. Then you use these test credentials (instead of your real ones) in IDC > Gateways > Authorize.Net.

Create your Authorize.Net test credentials via developer.authorize.net/sandbox/.


When using FirstData as a gateway, if you would like to set up up a test account, we recommend that you contact your FirstData account representative for help with this.