Get Started

Environments

Sandbox and production base URLs, and what changes between the two environments.

Tonder provides two environments for your integration:

  • Sandbox — for development and testing.
  • Production — for processing live transactions.

Each environment has its own set of base URLs and API credentials.

Use the correct base URL and keys for each environment. Using production keys in sandbox (or vice-versa) results in authentication errors.

Overview

EnvironmentPurposeDashboard
SandboxDevelopment, testing, and integration validationdashboard-stage.tonder.io
ProductionLive transactions with real fundsdashboard.tonder.io

Base URLs

ServiceSandboxProduction
API Direct (S2S)https://stage.tonder.io/api/v1/https://app.tonder.io/api/v1/
Hosted Checkouthttps://api-stage.tonder.io/checkout/v1/https://api.tonder.io/checkout/v1/
Card tokenizationhttps://token-sandbox.tonder.io/https://token.tonder.io/
Raw card data (PCI L1)https://process-sandbox.tonder.io/https://process.tonder.io/
Dashboardhttps://dashboard-stage.tonder.io/https://dashboard.tonder.io/

Base domains

DomainEnvironmentUsage
stage.tonder.ioSandboxStandard API, auth
app.tonder.ioProductionStandard API, auth
api-stage.tonder.ioSandboxHosted Checkout (checkout sessions) — see Hosted Checkout
api.tonder.ioProductionHosted Checkout (checkout sessions)
token-sandbox.tonder.ioSandboxCard tokenization service
token.tonder.ioProductionCard tokenization service
process-sandbox.tonder.ioSandboxRaw card data processing (PCI L1)
process.tonder.ioProductionRaw card data processing (PCI L1)

API credentials

Each environment uses a separate set of credentials (API key and secret key), available in the corresponding dashboard under Developers.

  • Never use production keys in your testing environment.
  • Never expose your keys in client-side code.
  • Store credentials securely on your server.
  • Rotate keys immediately if compromised.

Next steps

Was this page helpful?

On this page