What can be tested?
How to interpret this page
Not all features have full support in Sandbox. Some can be fully homologated, while others depend on specific behaviors, additional configurations, or resources that are only available in production.
Use this page as a reference during homologation to identify which features can be tested and which require additional procedures.
The indicators in the table should be interpreted as follows:
- ✅ Available for testing in Sandbox — the flow can be homologated normally.
- ⚠️ Available with restrictions — requires prerequisites, specific configurations, or behaves differently from production.
- ❌ Not available in Sandbox — the feature cannot be fully homologated in this environment.
ImportantWhen a feature is marked with ⚠️ or ❌, review the notes in the table itself and the related content before concluding the integration homologation.
Homologation recommendations
Before starting your tests, we recommend:
- properly configuring your Sandbox account;
- generating balance for financial tests;
- configuring webhooks;
- validating both success and failure scenarios;
- reviewing the specific limitations of each feature.
These precautions help reduce discrepancies between the behavior observed in Sandbox and the behavior expected in production.
Not all features are fully supported in the Sandbox. Some can be tested normally, others have restrictions, and some are not available in this environment.
Consider the indicators in the table below as follows:
- ✅ Can be tested normally in the Sandbox
- ⚠️ Can be tested with restrictions, prerequisites, or specific behavior
- ❌ Cannot be tested in the Sandbox or is not fully supported in this environment
Whenever you see a ⚠️ or ❌ indicator, review the explanatory sections of this guide before considering the flow fully validated.
| Description | Can it be tested? |
|---|---|
| Customers | |
| Creation of customers | ✅ |
| List customers | ✅ |
| Retrieve a single customer | ✅ |
| Update customers | ✅ |
| Deletion of customers | ✅ |
| Restore removed customer | ✅ |
| Payments | |
| Creation of payment | ✅ |
| Creation of with credit card | ✅ |
| Create a installment payment | ✅ |
| Create payment with split | ✅ |
| Retrieve a single payment | ✅ |
| List payments | ✅ |
| Update existing payment | ✅ |
| Tokenization of credit card | ✅ |
| Remove payment | ✅ |
| Restore removed payment | ✅ |
| Chargeback | ✅ |
| Get boleto's barcode | ✅ |
| Boleto layout with Pix QR Code | ❌ |
| Get PIX QR Code | ✅ |
| Confirm cash receipt | ✅ |
| Undo cash receipt confirmation | ✅ |
| Upload payment documents | ✅ |
| Update a payment document's settings | ✅ |
| List/Retrieve payment documents | ✅ |
| Delete a payment document | ✅ |
| Apply discounts, interest, and fines on boleto/Pix | ❌ |
| Installments | |
| List/Retrieve installments | ✅ |
| Remove installment | ✅ |
| Chargeback installment | ✅ |
| Subscriptions | |
| Create subscription | ✅ |
| List/Retrieve subscriptions | ✅ |
| List charges of a subscription | ✅ |
| Create subscription with credit card | ✅ |
| Update subscription | ✅ |
| Remove subscriptions | ✅ |
| List billing invoices of a subscription | ✅ |
| Create settings for invoice issuance | ✅ |
| Update settings for invoice issuance | ✅ |
| Retrieve settings for invoice issuance | ✅ |
| Remove settings for invoice issuance | ✅ |
| Payment Link | |
| Create a payment link | ✅ |
| Update a payment link | ✅ |
| Retrieve a payment link | ✅ |
| List payment links | ✅ |
| Remove a payment link | ✅ |
| Restore a payment link | ✅ |
| Add an image to a payment link | ✅ |
| Retrieve payment link image | ✅ |
| List payment link images | ✅ |
| Remove payment link image | ✅ |
| Set main image for payment link | ✅ |
| Notifications | |
| Update existing notification | ✅ |
| Batch update existing notification | ✅ |
| Email notifications | ✅ |
| SMS notifications | ✅ |
| WhatsApp notifications | ❌ |
| Transfers | |
| Transfer to ASAAS account | ✅ |
| Bank transfer via TED | ✅ |
| Bank transfer via PIX | ❌ |
| Transfer to another PIX key | ⚠️ - Transfers to existing keys in sandbox are possible |
| Retrieve a single transfer | ✅ |
| List transfers | ✅ |
| Advances | |
| Request advance | ✅ |
| Simulate advance | ❌ |
| Retrieve/List advances | ✅ |
| Debt Collections | |
| Create a debt collection | ❌ |
| Simulate a debt collection | ✅ |
| Retrieve debt collection | ❌ |
| List debt collections | ❌ |
| Resend documents | ❌ |
| Cancel debt collections | ❌ |
| Bill Payment | |
| Create a bill payment | ✅ |
| Simulate a bill payment | ✅ |
| List/Retrieve bill payments | ✅ |
| Cancel bill payment | ✅ |
| Mobile Recharges | |
| Request recharge | ✅ |
| Serasa Consultation | |
| Perform consultation | ❌ |
| Retrieve a consultation | ❌ |
| List consultations | ❌ |
| Statement | |
| Retrieve statement | ✅ |
| Financial Information | |
| Retrieve account balance | ✅ |
| Charge statistics | ✅ |
| Retrieve split values | ✅ |
| Account Information and Customization | |
| Retrieve commercial data | ✅ |
| Retrieve WalletId | ✅ |
| Save invoice customization | ✅ |
| Retrieve customization settings | ✅ |
| Retrieve ASAAS account number | ✅ |
| Invoices | |
| Schedule invoice | ✅ |
| Update invoice | ✅ |
| Retrieve an invoice | ✅ |
| List invoices | ✅ |
| Issue an invoice | ✅ |
| Cancel an invoice | ✅ |
| List municipal services | ✅ |
| Tax Information | |
| List municipal settings | ✅ |
| Create and update tax information | ✅ |
| Retrieve tax information | ✅ |
| Pix | |
| Create a key | ✅ |
| Retrieve a single transaction | ✅ |
| List transactions | ✅ |
| Cancel a scheduled transaction | ✅ |
| Create a static QRCode | ✅ |
| Decode a QRCode | ✅ |
| Pay a QRCode | ⚠️ - Available when using a QR Code compatible with the scenarios supported in Sandbox. See the Pix QR Code testing guide. |
| List keys | ✅ |
| Retrieve a single key | ✅ |
| Remove key | ❌ |
| Webhook Configuration | |
| Create or update Webhook setting | ✅ |
| Retrieve settings | ✅ |
| Asaas Account/Subaccounts | |
| Create account | ✅ |
| List accounts | ✅ |
| Sending documents via link (BaaS) | ⚠️ — Manual approval request needed for integration success team |
Features with restrictions or limitations
Some features have partial behavior or depend on specific conditions for homologation.
The most common scenarios are:
Features with restrictions (⚠️)
These features can be tested, but require additional procedures:
- Pix transfers depend on the use of specific Pix keys for homologation.
- Chargeback disputes require assistance from the Integration Success team.
- Document submission via link (BaaS) requires manual approval for testing.
Unavailable features (❌)
These features do not have full support in Sandbox or depend on external integrations that are not simulated in the environment:
- Bank slip layout with Pix QR Code.
- Application of discounts, interest, and penalties on bank slips/Pix.
- WhatsApp notifications.
- Anticipation simulation.
- Pix QR Code payment (when not supported by the specific scenario).
- Pix key removal.
AttentionA feature being unavailable in Sandbox does not mean it is unavailable in production. In many cases, the limitation exists only to simplify the homologation environment.
Best practices
Recommended
- Review the specific guides for each feature before homologation.
- Do not assume that all behaviors observed in Sandbox will be identical to production.
- Validate webhooks, status updates, and business rules whenever possible.
- Test both success and failure scenarios during homologation.
- Use only data intended for testing.
Related content
- How to configure your Sandbox account.
- Adding balance to a Sandbox account.
- How to test features in Sandbox.
- Testing transfers.
- Testing Pix QR Code payments.
- How to test critical actions.
- Account approval.
