Testing & Going Live

Sandbox and live are separate Orchestra accounts. You choose the account type when you register, and it cannot be changed later. The API is the same for both: the account behind your API key decides the environment.

Sandbox vs Production

Account	Use Case	Behavior
Sandbox	Development, testing, CI/CD	Every transaction runs in your provider’s test mode. No real money moves.
Live	Live customer transactions	Transactions run in your provider’s live mode. Real money moves.

The API base URL is the same for both accounts: https://api.orchestrasolutions.com

How Environments Work

A sandbox account always runs in test mode. This applies to every transaction, whatever credentials you put in its Payment Gateway Accounts. Live provider credentials do not make a sandbox account live.
A sandbox account cannot start live Payments Library sessions. A session request with mode set to LIVE returns 403 with the message “The user cannot make Live operations”.
Everything belongs to one account. API keys, Payment Gateway Accounts, eWallet Accounts and templates exist only in the account where you created them.

Setting Up for Testing

Quick Start with Mock PSPs

For immediate testing without external provider accounts, use Orchestra’s built-in mock payment gateways:

In the Portal, go to Payment Gateway Account > Create
Select NULLSuccess or NULLFailure as the gateway
Give it a name (e.g., “testSuccess”)
Leave credentials empty
Use the account name in your API calls

Mock PSPs simulate basic success/failure scenarios instantly, with no external dependencies. See Mock PSPs for complete details and limitations.

1. Create Test Payment Gateway Accounts

For comprehensive testing with real provider features, use your provider’s test/sandbox credentials:

Name: stripeTest
Gateway: Stripe
Credentials: sk_test_...

2. Use Sandbox API Keys

Generate your development API keys in your sandbox account. Label them clearly (e.g., “Development”, “CI/CD”).

Never use production API keys in development environments or commit them to version control.

3. Use Test Card Numbers

Each payment provider has test card numbers that simulate various scenarios:

Provider	Test Card	Notes
Stripe	`4111111111111111`	Successful charge
Stripe	`4000000000000002`	Card declined
Adyen	`4111111111111111`	Successful charge

Check your payment provider’s documentation for their full list of test cards and scenario simulations (3DS challenges, insufficient funds, etc.).

Payments Library Mode

When using the Payments Library, set the mode parameter in your session request:

{
  "operation": "CHARGE",
  "mode": "TEST",
  "amount": 25.00,
  "currencyCode": "USD",
  "paymentGatewayAccountId": "stripeTest"
}

Mode	Behavior
`TEST`	Sandbox transactions
`LIVE`	Production transactions

Going Live Checklist

When you’re ready to accept real payments:

Create an account again, this time with the Sandbox Account switch turned off. Your sandbox account stays as it is, so you can keep testing there.

Generate a Live API Key

Generate an API key in the live account. Keep it in environment variables or a secrets manager.

Recreate Your Setup

Nothing is copied from your sandbox account. In the live account, create again:

your Payment Gateway Accounts, with your providers’ live credentials
your eWallet Accounts
your templates

Using the same names as in sandbox means your code does not need to change.

Update Your Application

Switch your application to the live API key. For the Payments Library, change mode from TEST to LIVE.

Confirm Your Compliance Documents

Check which SAQ applies to you and request our AoC. See PCI Scope and Compliance.

Test with Small Amounts

Before full launch, process a few small real transactions to verify everything works end-to-end.

Running Both Environments

Keep one API key per account and choose it by environment:

// Sandbox key in development, live key in production
const apiKey = process.env.NODE_ENV === 'production'
  ? process.env.ORCHESTRA_LIVE_API_KEY
  : process.env.ORCHESTRA_SANDBOX_API_KEY;

const response = await fetch('https://api.orchestrasolutions.com/PaymentGateway/charge', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-Api-Key': apiKey
  },
  body: JSON.stringify({
    amount: 25.00,
    currency: 'USD',
    paymentGatewayAccountName: 'stripe',
    card: { ... }
  })
});

Best Practices

Separate Everything

Use a sandbox account for testing and a live account for production, each with its own API keys and environment variables.

Never Mix Credentials

Don’t use test credentials in production or vice versa. Label accounts clearly.

Automate Safely

CI/CD pipelines should only have access to test credentials. Production deploys should pull from secure secrets.

Monitor After Launch

Watch your first production transactions closely. Verify amounts, success rates, and provider responses.

Create Account

Add Payment Provider

Connect your gateways

Generate API Key

Create API credentials

API Reference

Authentication and endpoints

Start Here

Beyond the Quickstart

Concepts

Orchestra Payments Library Guides

Orchestra REST API Guides

Utilities

Merchant Account Setup

Support

Changelog

Sandbox vs Production

How Environments Work

Setting Up for Testing

Quick Start with Mock PSPs

1. Create Test Payment Gateway Accounts

2. Use Sandbox API Keys

3. Use Test Card Numbers

Payments Library Mode

Going Live Checklist

Running Both Environments

Best Practices

Separate Everything

Never Mix Credentials

Automate Safely

Monitor After Launch

Create Account

Add Payment Provider

Generate API Key

API Reference

​Sandbox vs Production

​How Environments Work

​Setting Up for Testing

​Quick Start with Mock PSPs

​1. Create Test Payment Gateway Accounts

​2. Use Sandbox API Keys

​3. Use Test Card Numbers

​Payments Library Mode

​Going Live Checklist

​Running Both Environments

​Best Practices

Separate Everything

Never Mix Credentials

Automate Safely

Monitor After Launch

​Related

Create Account

Add Payment Provider

Generate API Key

API Reference

Sandbox vs Production

How Environments Work

Setting Up for Testing

Quick Start with Mock PSPs

1. Create Test Payment Gateway Accounts

2. Use Sandbox API Keys

3. Use Test Card Numbers

Payments Library Mode

Going Live Checklist

Running Both Environments

Best Practices

Related