How to configure your Sandbox account

The Sandbox settings section allows you to simulate specific scenarios during integration development and homologation.

These settings provide autonomy to reproduce behaviors that would normally depend on approvals or operational processes in the production environment, allowing you to validate flows before deployment.

🚧

Important

Settings enabled in Sandbox are used exclusively for testing.

Enabling a feature in Sandbox does not mean it will automatically be available in production.

If your integration depends on these features in a production environment, consult your account manager.

When to use

Sandbox settings are recommended for:

• validating flows before deployment to production;
• reproducing specific scenarios during development;
• testing features that depend on commercial or operational approvals;
• homologating integrations without impacting real operations;
• anticipating expected behaviors of the production environment.

How Sandbox settings work

The available options allow you to change the behavior of the testing environment without affecting the production account.

Settings can be enabled and disabled at any time and only affect the Sandbox account.

📘

Important

Some features require specific enablement in production, even if they are available for testing in Sandbox.

What happens when a setting is enabled

The settings available on this screen act as homologation features and immediately change the behavior of the Sandbox account after activation.

In general, each setting has only two states:

When a setting is enabled, new tests executed in the account will consider the feature as active.

📘

Important

These changes affect only the Sandbox account where the setting was configured and do not produce any effect on production accounts.

Available features

Enable BaaS for subaccounts

Allows you to simulate the creation and use of subaccounts in Banking as a Service scenarios.

This setting is useful for validating integrations that operate with White Label structures or multiple accounts.

Learn more about BaaS subaccounts

📘

Important

Availability in production depends on applicable commercial and regulatory rules.

Enable card tokenization

Allows you to test the secure storage of card data and the use of tokens in future charges.

This setting is especially useful for:

• subscriptions;
• recurring payments;
• payments that do not require card details to be entered again.

Learn more about tokenization

📘

Important

The Sandbox behavior is intended exclusively for homologation and does not replace production enablement requirements.

Allow creation of foreign payers

Allows you to create international customers and validate flows involving foreign payers.

This feature is recommended for integrations that operate with customers outside Brazil.

⚠️

Important

Usage in production depends on specific account approval.

Configure charge-related limits

Allows you to define limits used during testing.

This setting facilitates validation of behaviors related to:

• minimum amount;
• maximum amount;
• issuance restrictions.

These limits are intended exclusively for homologation purposes.

Enable automatic approval of subaccounts

Allows you to simulate scenarios in which subaccounts are automatically approved.

This feature is useful for validating the complete flow of creating and using subaccounts without depending on manual processes.

📘

Important

Automatic approval in Sandbox does not represent the actual behavior of the production environment.

Example homologation flow

A White Label platform can use Sandbox settings to:

1. Enable BaaS.
2. Enable automatic approval of subaccounts.
3. Create a subaccount via API.
4. Test charges and receipts.
5. Validate webhooks.
6. Simulate the complete integration behavior before deploying to production.

Practical example

Consider a White Label platform that wants to validate the complete subaccount creation flow.

In this scenario, the setting can be used as follows:

1. Access the Sandbox settings.
2. Enable BaaS for subaccounts.
3. Enable automatic approval of subaccounts.
4. Create a subaccount using the account creation endpoint.
5. Use the returned API Key to perform operations on the subaccount.
6. Create customers, charges, and test webhooks.
7. Validate the expected integration behavior.

Simplified flow:

Enable BaaS
        ↓
Enable automatic approval
        ↓
Create subaccount
        ↓
Receive API Key
        ↓
Run tests
        ↓
Validate integration

This process allows you to homologate the entire subaccount journey before using the production environment.

Where to access

To configure your account, go to:

User Menu → My Account → Settings → Sandbox

Best practices

📘

Recommended

• Perform all homologation in Sandbox before using production.
• Do not assume that features available in Sandbox will be automatically enabled in production.
• Validate webhook behavior and API responses during testing.
• Use fictitious data whenever possible.
• Consider that some production flows may require additional approvals.

Differences between Sandbox and Production

Operational impacts

Sandbox settings are intended to facilitate integration homologation but do not replace the validations, approvals, and processes that exist in production.

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

Next steps

After configuring your Sandbox account, we recommend reviewing:

• Subaccount creation.
• Card tokenization.
• Webhook configuration.
• Automatic Pix.
• Credit card charges.
• API homologation guide.