Testing your Site

Testing your Site


Testing your Site

Whether you are using the Public Pages or our API, you need to verify your setup through real usage, both so you’ll know that your configuration options are correct, and so you’ll know more about what your customers will experience.

Please test your Site before going Live! Test the cycle of Subscription changes, cancellations, Invoices or Statements (if applicable), refunds, emails, etc..

Chargify sites that are in test mode will work with both the Chargify Test Gateway and with the test gateways provided by the gateways like Authorize.Net, PaymentExpress, Beanstream, Stripe, etc. Note that all of the major gateway providers will give you a free test account (sometimes called a “developer” or “sandbox” account) so that you can test your integration.

When you’re ready to go live, you can use the Clear site data link at the top of the web UI to clear all of your test data. You may choose to keep your product set up at this time. Our section on Clearing Site Data goes in to more detail.

Test mode sites are limited to a maximum of 500 of each of coupons, subscriptions, customers and products.

Please note that data in Test sites is NOT guaranteed to be retained, however we normally allow test subscriptions to remain active for several months. After that time, they may be automatically canceled to preserve system resources.

Real customers added while in test mode

Note: Do not sign up real customers while you are in test mode. You cannot bring subscriptions with you when you change from test mode to live mode..

When your site has no active subscriptions, you may change it in and out of test mode. So, once you clear your subscriptions, you can move your site to live mode and change your gateway credentials to those for your production payment gateway.

It is our recommendation to also run a handful of tests against your live gateway. This testing can reveal misconfigurations in your gateway settings for things like AVS (Address Verification Service) and other fraud filter checks. You can always void these transactions later through your payment gateway interface. It is worth the few cents in transaction fees you will incur to verify your setup before your Customers attempt to use it.

Changing your site from Test to Live

If you convert a site from “test” mode to “live” mode, you should configure your gateway before you take any signups. If you take signups while you are still on the Test gateway, you will have difficulty switching later.

  1. Visit your main Sites page and click on ‘Clone’ to clone your test site for future testing.
  2. Cancel all active subscriptions.
  3. If you are on Chargify’s free plan, upgrade to a paid plan.
  4. Enter your payment gateway credentials under your Site’s Settings > Payment Gateway section
  5. Visit your Sites page > click ‘Change Mode / Edit’ for the desired Site > In the “Test Mode” section, select ‘No’ > Save
  6. Perform a test transaction (actual signup) to ensure gateway connection is working properly before allowing your customers to sign up. If no errors are received, and the subscription is created, you are ready to begin signing up new customers!

Determine if your Site is in Live Mode or Test Mode

You can easily tell if your site is in Live Mode or Test Mode. If your site is in Test Mode, you will see the following:

  • The Go Live button will display a grey circle
  • Chargify will show you a Go Live Guide
  • You can hide this at any time by selecting Hide Setup Guide

If your site is in Live Mode, you will not be able to display these options:

  • Your site will prominently display Live Mode with a green circle circle
  • You will not have the option to Clear Current Site Data under the Site Menu
  • The Setup Guide will not be available Hide Setup Guide

Maximum Limits for Test Sites

Newly created accounts will have their test-mode sites limited to a maximum of 500 of each of coupons, subscriptions, customers and products, instead of being unlimited. If too many records are created, an error message will be returned such as “Would exceed the limit of 500 subscriptions”

This will help ensure the stability and performance of the platform, by preventing merchants from creating too many unnecessary records.

Test sites are intended for basic manual testing and confirming that your API integration code works as expected. Unfortunately, some merchants may accidentally leave these automatic integrations running continuously on a test site, leading to extremely large numbers of records being created.

Existing accounts who are currently under this limit will not be able to exceed it going forward.

We’ll reach out to any merchants who are currently exceeding these new limits to ensure integrations don’t suddenly break.