Skip to main content
Kelviq’s sandbox is a separate environment for development and testing. You can configure products and plans, create customers, exercise checkout flows, and test your integration without affecting your live organization or processing real payments.

​
How isolation works

Sandbox and production use separate data and credentials. This separation prevents development activity from changing live customer or billing data. Before launch, configure the resources your integration needs in production and replace all sandbox credentials and URLs.

​
Get started

  1. Sign in to the Kelviq dashboard.
  2. Open the organization dropdown and click Enter sandbox.
  3. Create the products, plans, prices, and other test data you need.
  4. Open Settings → API keys and copy the sandbox key required by your integration.
Never use a production Server API Key in test code. Store Server API Keys in environment variables and use Client API Keys only in supported browser integrations.

​
Connect to the sandbox API

Use the sandbox hosts with sandbox-scoped credentials: For example:
Changing only the URL is not enough: the request must also use an API key created while the dashboard is in Sandbox mode.

​
Use the sandbox with an SDK

Set environment to sandbox when initializing an official SDK.
See the Node SDK, Python SDK, or frontend SDK guides for full setup instructions.

​
Test checkout

Create a checkout in the sandbox and use Stripe test card details. Use any future expiration date and a valid test CVC.
Do not enter a real card number in the sandbox.
After payment, confirm that the test order, customer, subscription, and entitlements have the expected state in Sandbox mode.

​
Test a subscription renewal

Daily billing is not enabled by default. Any sandbox organization can request it by contacting Kelviq support.
After Daily billing is enabled, use it to test a renewal without waiting for a monthly or yearly billing cycle.
  1. Enter Sandbox mode in the Kelviq dashboard.
  2. Open the test plan you want to use.
  3. Under Billing cycles, select Daily and enter a test price.
  4. Publish the plan.
  5. Start a subscription with a sandbox test card.
  6. After the next billing cycle, check the order, invoice, subscription status, and entitlements in Sandbox mode.
If you create the checkout session through the API, set chargePeriod to DAILY:

​
Can I test production with my own card?

No. Do not place a live order using your own card just to test production credentials. Payment providers can treat a self-payment as suspicious and block the card, even when the amount is small. There is no safe minimum price for this test. Use one of these options instead:
  • Keep payment and renewal testing in Sandbox.
  • If you need to inspect the production checkout, create a 100% discount code so no real payment is collected.
  • Check production credentials, URLs, and environment settings without completing a purchase.

​
Prepare for production

Before accepting live payments:
  1. Complete the required business review and payout setup.
  2. Configure and publish your production products and plans.
  3. Replace sandbox API keys with production API keys.
  4. Replace sandbox base URLs or set each SDK’s environment to production.
  5. Run a final check that no sandbox credentials or hosts remain in your production configuration.
Use clearly named variables such as KELVIQ_SANDBOX_SERVER_API_KEY and KELVIQ_PRODUCTION_SERVER_API_KEY to reduce the chance of mixing environments.