Configure your Sandbox account features

Sandbox settings let you enable features and simulate specific scenarios while developing your integration.

These changes affect only the Sandbox account and do not move real money.

When to use it

Use these settings to:

• test features that require enablement;
• reproduce specific scenarios;
• validate subaccount flows;
• validate tokenization and recurring charges;
• test integrations before go-live.

1. Access the settings

In the Sandbox interface, go to:

User menu → My account → Settings → Sandbox

2. Enable the necessary features

Settings can be turned on or off at any time.

Changes affect only the account in which they were made.

Available features

BaaS for subaccounts

Lets you test creating and using subaccounts in a BaaS operation.

Use this setting to validate flows in which your platform creates and manages customer accounts through the API.

Learn more about the evaluation period for BaaS subaccounts.

Card tokenization

Lets you test generating and using card tokens in future charges.

This feature can be used in flows such as:

• subscriptions;
• recurring charges;
• new payments with an already tokenized card.

Learn more about tokenization.

Foreign payers

Lets you create international customers and validate flows with payers from other countries.

Using this feature in Production depends on it being enabled for the account.

Charge limits

Lets you configure limits used in tests, such as:

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

The configured values are for validation testing only.

Subaccount auto-approval

Lets you simulate automatic approval of subaccounts created in the Sandbox.

This option makes it easier to fully test the integration without depending on a manual review.

3. Validate the complete flow

To validate an integration with BaaS subaccounts:

1. Enable BaaS.
2. Turn on subaccount auto-approval.
3. Create a subaccount through the API.
4. Store the returned API key.
5. Perform operations on the subaccount.
6. Validate that Webhooks are received.
7. Check that your application processed the events correctly.

Enable BaaS
        ↓
Turn on auto-approval
        ↓
Create subaccount
        ↓
Get the API key
        ↓
Run operations
        ↓
Validate Webhooks

Differences between Sandbox and Production

Before going to Production

Confirm:

• which features need to be enabled;
• whether the critical flows have been validated;
• whether Webhooks are configured;
• whether the application handles errors and status changes;
• whether the Sandbox credentials have been replaced;
• whether any fictitious data remains in the configuration;
• whether the differences between environments have been taken into account.

Next steps

• Create a subaccount
• Learn about Asaas BaaS
• Test card charges
• Configure your Webhooks
• See what can be tested in the Sandbox