How to Test Features in Sandbox

The Sandbox environment allows you to validate most of the flows available in the API before using them in production.

Although its behavior is similar to the production environment, some features have specific homologation mechanisms designed to facilitate testing. In certain scenarios, it is possible to simulate events, manually confirm operations, or use resources available exclusively in the Sandbox environment.

For this reason, some flows require procedures that differ from those used in production.

When to use

This section is recommended for developers who want to:

validate integrations before deployment to production;
test financial flows without moving real funds;
homologate webhook delivery;
validate application business rules;
simulate specific platform scenarios;
understand behaviors exclusive to the Sandbox environment.

How the homologation process works

In a typical integration, the testing process usually follows the journey below:

Configure Sandbox account
        ↓
Create test resources
(customers, charges, etc.)
        ↓
Execute operations
        ↓
Simulate events
        ↓
Receive webhooks
        ↓
Validate application behavior
        ↓
Homologate integration

Depending on the feature being tested, there may be specific simulation mechanisms that allow the expected behavior to be reproduced without requiring real financial processing.

Differences from production

Although Sandbox reproduces a large portion of the platform's behavior, there are important differences that should be considered during testing:

some operations can be simulated manually;
certain internal validations are simplified;
some features depend on specific Sandbox settings;
not all external integrations behave identically to the production environment;
the availability of a feature in Sandbox does not guarantee its enablement in production.

For this reason, it is always recommended to validate the necessary requirements before going live.

🚧
Important
Homologation in Sandbox reduces risks during development but does not replace the validations, commercial approvals, and operational requirements that exist in the production environment.

Features with specific testing flows

The pages below provide detailed instructions for homologating the main resources available in Sandbox:

What can be tested

Not all platform features have full coverage in the Sandbox environment.

Before starting homologation, consult the page:

What can and cannot be tested

It provides the updated list of resources available for testing and their respective limitations.

Testing calls directly in the documentation

In addition to the tests performed through your application, it is also possible to execute calls directly from the API documentation using Sandbox credentials.

This feature is useful for:

validating payloads;
testing parameters;
analyzing API responses;
quickly reproducing scenarios during development.

See:

How to test calls directly in the documentation

Best practices

📘
Recommended

Perform tests in Sandbox before using production.

Validate both synchronous responses and received webhooks.

Test both success and error scenarios whenever possible.

Use fictitious data during homologation.

Consult the specific pages for each feature to understand Sandbox-specific behaviors.

A complete homologation significantly reduces the need for adjustments after going live.