This article provides information on how to “test” the process of buying and managing a subscription with SubscriptionBridge.

How and what to test can vary depending on the payment gateway that you have associated with your SubscriptionBridge-based store. So the rest of the article is divided into sections that are specific to each payment system.

The Authorize.Net Automated Recurring Billing (ARB) system does not have a testing (or “sandbox”) environment. Authorize.Net Advanced Integration Method (AIM) does, but not the Recurring Billing system. So there is no way to create a “test” subscription and then have it process recurring payments in a test mode.

However, you can test the system in a live environment without actually charging the credit cards used in the tests. This is because when a transaction is processed by the ARB system, it is passed to the main Authorize.Net virtual terminal and it appears under Unsettled Transactions, awaiting settlement. Recurring payments are processed at around 2 AM PST, and those same payments are not captured until the afternoon (PST). So there are several hours in which the payments remain unsettled and can be voided before they settled.

For instance, this means that you can do the following:

• Purchase a subscription via the built-in SubscriptionBridge shopping cart, using a real credit card
• An ARB subscription will be setup in Authorize.net
• ARB transactions are processed around 2 AM PST. Those transactions then appear under Unsettled Transactions until the time they are settled later that day (typically late afternoon, PST). So you have several hours in which you can:
  • Locate the transaction under Unsettled Transactions
  • Click on the transaction ID
  • Click on the VOID button to void it.
    Note that voided transaction may still appear in your credit card statement for a few days as the corresponding amount had been pre-authorized and was awaiting settlement. They will automatically disappear after a few days (this can take up to 2 weeks, according to Authorize.Net).

By using this approach, you are testing the system in a fully “live” environment. When recurring payments are processed, information will be posted to SubscriptionBridge via the [:authorize.net#add-silent-post-url|Silent Post URL]. The only difference compared to what you will do with “real” transactions consists in the voiding of the payment before it is settled.

To test the system and simulate different scenarios, setup a short subscription (e.g. a subscription with a weekly payment interval and a week-long free trial, for example). You will then see SubscriptionBridge go through a series of “events” associated with the subscription (E.g. trial expiration reminder, subscription payment notifications, etc.). Note that Authorize.Net requires that the billing period be weekly or longer (i.e. you cannot setup a daily subscription, although that would be useful for testing purposes).

PayPal has a testing (“sandbox”) environment. You can find it at https://developer.paypal.com/

The PayPal Sandbox mimics exactly the live PayPal system. So to use test SubscriptionBridge with PayPal:

1. Create a PayPal Website Payments Pro sandbox account, just like you would with a regular account
2. Set it up exactly as you would with your “live” account. This includes…
   1. Requesting your API credentials
   2. Requesting that Recurring Payments are added to your sandbox account
3. Log into your SubscriptionBridge Merchant Center
4. Enter the PayPal API credentials on the payment tab

You can now use SubscriptionBridge with your sandbox Website Payments Pro account.

- This section is under construction.