An API sandbox gives developers a place to test requests and responses separately from the production service. Stripe describes its sandboxes as isolated environments for testing without real payments. That is Stripe’s documented behaviour, so check the equivalent rules for each travel or payment provider. Source: Stripe: sandboxes

A travel example

For a booking project, ask your developer to demonstrate a successful test reservation, a changed price and a failed request using the provider’s approved test setup. Keep a record of the expected result for each scenario. These are suggested tests, not a statement that every sandbox offers them.

Before running a test

Confirm the correct address, credentials and any required test flags. Agree which actions can contact suppliers or customers. Use invented traveller details unless there is a specific, approved reason to use personal information.

What a sandbox does not prove

Treat a sandbox pass as evidence for the scenario tested. Before launch, agree a controlled production verification with the provider, including how to identify and clean up any test transaction. This checks the actual configuration rather than assuming a successful test environment guarantees the live result.

Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.