.svg)
.svg)
.svg)
.svg)
.svg)
The unified orchestration layer for wallets and alternative payments
.svg)
The secure repository for all your payment methods
.svg)
Workflow-driven payments intelligence for smarter routing and higher auth rates
.svg)
A flexible fraud and authentication layer. Instantly add advanced fraud tools and 3DS
One integration to sell inside ChatGPT, Gemini, and every agentic platform
Coming soon
The unified orchestration layer for wallets and alternative payments
The secure repository for all your payment methods
Workflow-driven payments intelligence for smarter routing and higher auth rates
A flexible fraud and authentication layer. Instantly add advanced fraud tools and 3DS
One integration to sell inside ChatGPT, Gemini, and every agentic platform
Coming soon
Sandbox / Test Environment
A sandbox, also called a test environment, is an isolated version of a payment provider's platform that allows developers to build, test, and validate payment integrations without processing real transactions or moving real money. The sandbox mirrors the behavior and API interface of the production environment, using test card numbers, simulated authorization responses, and dummy transaction data in place of live payment instruments.
Payment sandboxes are indispensable for safe development. Building a payment integration directly against a production environment would mean real card charges on real accounts every time a developer runs a test. Sandboxes allow development and QA teams to test every scenario, successful payments, declines, network errors, Chargeback workflows, 3DS authentication flows, and Webhook event handling, without financial consequences.
Well-designed sandboxes are accurate simulations of production behavior, not simplified proxies. A sandbox that cannot reproduce the edge cases a production system encounters, specific decline codes, Soft Decline vs. Hard Decline behavior, Frictionless Authentication vs. Step-Up Authentication in 3DS, creates a false sense of security and produces integrations that behave unexpectedly in production. Evaluating the fidelity of a payment provider's sandbox is a meaningful part of evaluating the provider itself.
Spreedly provides a test gateway and sandbox capabilities that support the full range of transaction types, including 3DS flows, Alternative Payment Methods (APMs), and Vault operations. The Spreedly sandbox is specifically designed to mirror production behavior closely, so integrations built in test reliably carry over to live operation.
Frequently Asked Questions
What are test card numbers and how do they work?
Test card numbers are fake card numbers, numbers that conform to the Luhn algorithm used to validate card numbers, but are not associated with real accounts, that payment providers configure their sandboxes to recognize and respond to in predictable ways. For example, a provider might configure card number 4111111111111111 to always return an authorization success, and 4000000000000002 to always return a decline.
Should a merchant use a production gateway in sandbox mode or a dedicated test gateway?
Both approaches are used in practice, and the right choice depends on the complexity of the integration. A dedicated test gateway (like Spreedly's test gateway) provides a fully isolated test environment with no risk of accidentally affecting production data. A production gateway in sandbox mode tests more realistic gateway behavior but carries the risk of misconfiguration leading to unintended production activity.
How should a merchant manage the transition from sandbox to production?
The transition should be treated as a formal go-live process, not just a credential swap. Before going live, the merchant should test all critical transaction paths in the sandbox with scenarios matching expected production behavior, ensure Webhook endpoints are configured and tested for both environments, confirm that production PCI DSS controls are in place, and complete any required gateway account setup (including KYB checks and compliance documentation).
Related Terms
