Test the Payment Processor

How Can I Run A Full Test of My Page?

Eric Knopf avatar
Written by Eric Knopf
Updated over a week ago

A tester payment processor is a fake processor that allows you to use a dummy credit card so you can test reporting, exports and integrations. This is useful for testing how data is going to save, appear and work without having to charge real cards and refund them.

Important (!) - Data collected when using a tester payment processor cannot be deleted. It is strongly advised you link the tester payment processor on a duplicate page instead of your primary registration page.

Please note: this is only available to GivingFuel customers who are on the Pro and Enterprise Plan.

This article will cover:

  • Adding A Tester Payment Processor

  • Linking The Tester Payment Processor To Your Test Page

  • Running Tests On Your Page

  • Common Uses

  • FAQs

Adding a Tester Payment Processor

Select Tester (For Testing Only) from the Payment Processor dropdown.

Input fake credentials (abcdef / 12345) as your ID and Merchant Key.

Linking the Tester Payment Processor To Your Test Page

Edit the page you want to link to a tester processor. When you hit publish, you will see a dropdown to select a processor. Choose the 'Tester (For Testing Only).

Important (!) When linked to a tester processor, you page will appear exactly like it will when linked to a real processor. Make sure you do not share your page to potential registrants when it is linked to a tester processor as people will not be able to pay with real cards.

Running Tests On Your Page

Complete your page as usual, but when you reach the billing section of your page, enter a dummy credit card of 4111-1111-1111-1111. You can enter expiration date as long as it’s in the future and any cvv. You can also enter any billing name and address you choose. Unlike when using preview mode, when you submit on a page linked to a tester payment processor, the data will be saved.

Please note: Do not use $5 as a transaction amount as it is designed to fake a decline message. See triggering errors using tester processor at the bottom of this article.

Here is what it should look like when submitting a page with a dummy credit card.

Common Uses

The following use cases are helpful for those who use a tester processor.

  • Testing 3rd party integrations with Zapier to verify how data appears

  • Examining how exports will work and function with sample data

  • Testing webhooks or API related tests

  • Testing scanning app and process with dummy data


Am I charged RegFox fees for registrations that use the tester gateway?

No fees are charged that run through the tester gateway.

What's the difference between a tester processor and preview mode?

If you hit "Preview" you can go through the entire form. It won't charge your card or save/reference any reporting data. You can see the confirmation page and it will send you a confirmation email. That's the best way to test the page flow.

While running tests with a tester payment processor won't charge a card either, it will pull information into the backend reporting.

Can I delete transactions that were run on a tester processor?

No, they will function the same as any transaction in your account, which cannot be deleted. We highly recommend running all tests on a copy of your page to prevent any tester data from skewing live reporting and analytics.

Acceptable Dummy Cards:

Dummy Visa Card: 4111-1111-1111-1111
Dummy American Express: 3782-8224-6310-005
Dummy Mastercard: 5555555555554444

How do I test a decline?

If you want to trigger an error of a decline with a tester payment processor, use a $5 transaction. That will trigger a decline on the page.

Did this answer your question?