You must test your integration in the sandbox environment before you move to the live environment. For more information, see Test transactions in the sandbox.
This topic describes how to move your integration from the sandbox environment to the live environment.
The sandbox and live environments are separate. Configuration and data that you create in the sandbox environment, such as gateway accounts, payment forms, and API keys, are not available in the live environment. For more information, see Environments.
Complete the following in your code and configuration:
- Create live API keys. In the live environment, create a secret key and, if your integration uses a payment form library, a publishable key. For more information, see API keys.
- Replace the sandbox API keys in your integration with the live keys. Sandbox keys start with
sk_sandbox_andpk_sandbox_. Live keys start withsk_live_andpk_live_. - Point your integration at the live environment:
- Rebilly API: Use
https://api.rebilly.cominstead ofhttps://api-sandbox.rebilly.com. - Rebilly JS SDK: Set
sandbox: false. - Rebilly Instruments: Set
apiMode: "live".
- Rebilly API: Use
- Confirm the organization ID and website ID that your integration uses. In the live environment, in the left navigation bar, press Settings, then in the Management section, press My organization & websites.
- If your integration uses webhooks, update the webhook URL to your production endpoint and verify signatures against the live public key. For more information, see Webhook configuration.
Check that each of the following exists in the live environment, and create it if it does not:
- Payment gateway accounts with your live gateway credentials. The
TestProcessorgateway is only available in the sandbox environment. - Products and pricing plans.
- Organization and website information, including the billing descriptor and support contact details.
- Hosted payment forms, if you use them.
- Webhooks, if you use them.
- Team members and their permissions, if required.
Live transactions create real charges. Plan your tests carefully and keep the amounts small.
- Limit the payment gateway to one, or a small number of, test customer IDs. For more information, see Set up a payment gateway - Configure additional filters.
- Define a series of small-value test transactions for various scenarios, and test these using all enabled card types and payment methods.
- Test the checkout flow on your website.
- Subscribe to a plan and confirm that the card is charged immediately.
- Cancel a subscription. For more information, see Cancel a subscription.
- Issue a partial and a full refund. For more information, see Refund transactions.
- Confirm that email notifications and webhooks are received.
- Log in to your payment gateway account and confirm that the test transactions are present.
- Remove the customer ID filter from the payment gateway.
If you use an embedded checkout page with a Rebilly API integration, you must use an SSL certificate. If you use a Rebilly hosted payment form, you do not require an SSL certificate. For more information, see Hosted payment forms.