← Resource centre

POLICIES

Developer and sandbox terms

Rules for using the test environment and building integrations.

Policy version · 21 September 2026. Read together with the service terms and your applicable written agreement.
01

Test-only use

The sandbox is a simulation environment. It does not move money, prove provider settlement or certify an integration for production. Use synthetic data and your own account. Test keys are personal account credentials and must be kept out of public code and customer browsers.

02

Limits and availability

Each account is limited to 1,000 test intents. Registration and sign-in are subject to attempt limits. Test records and interfaces may evolve as the service develops. The sandbox does not carry a published production availability guarantee or a promise of permanent data retention.

03

Responsibility for integration code

You are responsible for validating input, safeguarding credentials, verifying live webhooks and preventing duplicate fulfilment in your systems. Do not treat sandbox lifecycle success as a replacement for testing actual receipt formats, network outages and activation recovery.

04

Moving to production

Live registration and a verified public webhook are separate steps. Provider availability, commercial terms and operational readiness must be confirmed for the intended deployment. Using the sandbox does not grant rights to provider APIs, card acceptance or a regulated financial service.

KEEP EXPLORING

Your next connection starts here.