This guide explains how to configure and use test payment information for credit cards and electronic checks within the UltraCart platform. Utilizing test payments allows merchants to test checkout functionality without processing live transactions.

Overview

While performing real transactions is the best way for new merchants to test their payment gateway, there are scenarios, especially for live stores, where testing other configurations without incurring actual charges is necessary. UltraCart provides a mechanism to configure specific payment information that will automatically approve as a test payment, eliminating the need to void or reverse transactions.

Prerequisites

• Access to the UltraCart administrative interface.

• Understanding of your store's payment gateway configuration (if testing related functionality).

• User permissions required: Operations → Edit Settings

Test Credit Cards

Setup test cards within the Credit and Debit Cards settings section. Make sure the toggle in the top left of Credit and Debit Cards is turned on and click Settings to open the Credit and Debit cards dialog. Then scroll down to the Test Credit Cards section, and click new to create a new test credit card.

Open

Create Test Credit Card

When creating or editing a test credit card entry in UltraCart, you configure the test card number and define how orders placed using this test card will be processed.

Open

Credit Card Number

• This field allows you to enter the credit card number that will be recognized by the system as a test card.

• You can enter a standard test number (such as those listed in the Common Test Card Numbers section) or any other valid-looking number you wish to designate as a test number.

Order Handling Options

This section determines how orders placed using this specific test credit card will be processed by the UltraCart system. You must select one of the following radio button options:

• Skip payment gateway, consider payment processed, then have the order ship: This option bypasses the actual payment gateway and marks the order as paid. The order will then proceed through your standard order flow, including queuing for shipment if applicable. This is useful for testing the entire order lifecycle, including fulfillment integration.

• Skip payment gateway, consider payment processed, then reject to prevent shipment: This option also bypasses the payment gateway and marks the order as paid but immediately flags the order to be rejected. This prevents the order from proceeding to the shipping department. This is suitable for testing order creation and processing without involving fulfillment. Note that immediate rejection might affect some post-order processing steps like affiliate tracking or third-party marketing service subscriptions.

• Skip payment gateway, consider payment processed, then complete order to prevent shipment: Similar to the previous option, this bypasses the payment gateway and marks the order as paid while preventing shipment. However, this option allows most post-order placement processes (like affiliate tracking and subscriptions to third-party services) to occur, unlike the "reject" option.

• Keep order in accounts receivable and place a note on it: This is often the safest default setting for general testing. The order is created and marked as a test order, then placed in the Accounts Receivable queue. From Accounts Receivable, you can manually review, process, or delete the test order.

Additional Processing Options

Below the order handling radio buttons, there are checkboxes to control other aspects of test order processing:

• Skip affiliate transaction processing: When checked (default), this prevents the test order from interacting with UltraCart's internal affiliate system.

• Skip fraud filter: When checked (default), this causes UltraCart to bypass all configured fraud filters for orders placed with this test card.

• Skip conversion pixels: When unchecked (default), this allows UltraCart to skip processing any configured conversion pixels (like Google Analytics) for the test order.

Common Test Card Numbers

The following table of numbers are common test credit card sequences that will pass the LUHN-10 algorithm check for a valid credit card sequence.

Electronic Checks

Open

Test Electronic Check Editor Options

Open

The Test Electronic Check editor page provides a similar set of options as the Test Credit Card editor page, tailored for electronic check details.

• Bank Routing Number: Enter the test bank routing number.

• Bank Account Number: Enter the test bank account number.

The "How do you want to handle the payment and affiliate transaction processing?" section on the Electronic Check editor page contains the exact same order handling and additional processing options as described above for the Test Credit Card editor. You can configure test electronic checks to skip the payment gateway, control shipment, and manage affiliate/fraud/pixel processing in the same manner as test credit cards.

• Skip payment gateway, consider payment processed, then have the order ship.

• Skip payment gateway, consider payment processed, then reject to prevent shipment.

• Skip payment gateway, consider payment processed, then complete order to prevent shipment.

• Keep order in accounts receivable and place a note on it.

• Skip affiliate transaction processing.

• Skip fraud filter.

• Skip conversion pixels.

Common Configuration Settings for the Test CC and Test E-Checks:

"How do you want to handle the payment and affiliate management processing?"

Depending on your testing scenario you may need to adjust the handling for orders pplaced using the test credit card (or ehceck).
There are four options for how the order will be processed:

Remaining Checkbox settings

Seeing Test Orders In Accounts Receivable

If you place a test order and the handling setting is configured to "Keep order in accounts receivable and place a note on it.",
then it will appear in your Accounts Receivable color coded purple as shown below:

Within the test order table the test orders checkbox is highlighted with the light blue color.

Open

There is a delete test orders button that you can click that will delete all the test orders in one single action from the Accounts Receivable area.

Frequently Asked Questions

Q: Why should I use test payment information instead of live transactions for testing? A: While performing real transactions is the best way for new merchants to test their payment gateway, for live stores, testing other configurations without incurring actual charges is necessary. Using test credit card or electronic check numbers removes the hassle of voiding or reversing charges on real credit cards or checking accounts.  

Q: How do the "One per Customer" settings on my items interact with test orders? A: The "One per Customer" setting does not apply to test orders. If you use a test credit card on an order, this setting is bypassed. This is intended to prevent roadblocks that would stop a test order from being placed.  

Q: What are the different order handling options for test payments, and when should I use each one? A: When configuring a test credit card or electronic check, you can define how orders placed with it will be processed. There are four primary options:  

• Skip payment gateway, consider payment processed, then have the order ship: This bypasses the payment gateway, marks the order as paid, and allows it to proceed through your standard order flow, including queuing for shipment. Use this for testing the entire order lifecycle, including fulfillment integration.  

• Skip payment gateway, consider payment processed, then reject to prevent shipment: This bypasses the payment gateway, marks the order as paid, but immediately flags it for rejection to prevent it from going to shipping. This is suitable for testing order creation and processing without involving fulfillment. Note that immediate rejection might affect some post-order processing steps like affiliate tracking or third-party marketing service subscriptions.  

• Skip payment gateway, consider payment processed, then complete order to prevent shipment: Similar to the "reject" option, this bypasses the payment gateway and marks the order as paid while preventing shipment. However, this option allows most post-order placement processes (like affiliate tracking and subscriptions to third-party services) to occur.  

• Keep order in accounts receivable and place a note on it: This is often the safest default setting for general testing. The order is created, marked as a test order, and placed in the Accounts Receivable queue. From Accounts Receivable, you can manually review, process, or delete the test order.  
  
  

Q: Where can I find a list of common test credit card numbers to use? A: The document provides a table of common test credit card sequences that pass the LUHN-10 algorithm check for a valid credit card sequence. These include numbers for American Express, Diners Club, Discover, JCB, MasterCard, and Visa.  

Q: Is configuring a test electronic check different from configuring a test credit card? A: The Test Electronic Check editor page provides a similar set of options as the Test Credit Card editor page, tailored for electronic check details. You will enter a test bank routing number and bank account number. The order handling and additional processing options are the exact same as those for test credit cards.  

Q: How can I see test orders that are set to "Keep order in accounts receivable" and delete them? A: If you place a test order with the handling setting configured to "Keep order in accounts receivable and place a note on it," it will appear in your Accounts Receivable queue, color-coded purple. You can find this in the UltraCart interface under Home -> Operations (Order Management) -> Accounts Receivable. There is a "Delete Test Orders" button in the Accounts Receivable area that allows you to delete all test orders in one action.  

Q: What do the "Skip" checkboxes for affiliate transaction processing, fraud filter, and conversion pixels do for test orders? A: These checkboxes control additional processing aspects for test orders.  

• Skip affiliate transaction processing: When checked (default), this prevents the test order from interacting with UltraCart's internal affiliate system.  

• Skip fraud filter: When checked (default), this causes UltraCart to bypass all configured fraud filters for orders placed with this test card.  

• Skip conversion pixels: When unchecked (default), this allows UltraCart to skip processing any configured conversion pixels (like Google Analytics) for the test order.