FAQ
Frequently asked questions about the Nuvemshop module
This section gathers the main questions about the integration between Asaas and Nuvemshop.
The official plugin allows you to use Asaas as the store's payment gateway, processing orders through Pix, bank slip, and credit card.
In addition to the most common questions, this page presents limitations, important behaviors, and recommendations for using the integration.
Important integration rules
Before using the plugin, consider that:
- the integration operates exclusively using the Asaas production account;
- the plugin does not support the Sandbox environment;
- recurring payments are not supported by Nuvemshop;
- installments are only allowed for credit card payments;
- interest rules are configured during module installation;
- notifications between platforms are automatically performed through webhooks.
Important settings and parameters
During module installation and configuration, some parameters directly influence the behavior of the integration:
| Configuration | Purpose |
|---|---|
| API Key | Credential used to connect the store to the Asaas account |
| Maximum number of installments | Defines the maximum number of installments displayed at checkout |
| Interest per installment | Allows configuring specific rates for each number of installments |
| Minimum installment amount | Limits the installment options available to the customer |
| Bank slip due date | Defines how many days the bank slip will remain valid |
| Pix expiration period | Defines how long the Pix payment can be completed before expiration |
These settings can be changed in the module configuration and directly impact the customer shopping experience.
Is it possible to use the plugin in the Sandbox environment?
No.
The connection with the store is performed exclusively using your Asaas production account.
AttentionSince there is no Sandbox support, it is recommended to use low amounts and perform controlled test purchases before making the store available to customers.
Can I offer debit card payments?
No.
Currently, the integration only supports:
- Pix;
- bank slip;
- credit card.
Is it possible to offer installment payments?
Yes.
Installments are supported exclusively for credit card payments.
The maximum number of installments and interest rules are defined during module configuration.
Is it possible to apply interest to installments?
Yes.
When installments are enabled, the integration allows configuring specific interest rates for each number of installments.
These rules are automatically applied at checkout and directly influence the final amount displayed to the customer.
ImportantThe minimum amount per installment may also limit the number of installments available for certain purchases.
Is it possible to manage subscriptions through Nuvemshop?
No.
Since Nuvemshop is an e-commerce platform, it does not support recurring charges.
If you need to work with subscriptions, it is recommended to use the subscription features directly in Asaas through the API or platform interface.
Will I receive payment updates?
Yes.
During module installation, communication between Asaas and Nuvemshop is automatically configured.
Whenever a payment change occurs, the store will receive updates to synchronize the order.
Among the most common events are:
- payment confirmed;
- pending payment;
- cancellation;
- Pix expiration;
- bank slip due date expiration;
- refund.
How do notifications work between the platforms?
Synchronization between Asaas and Nuvemshop is automatically performed through webhooks.
These notifications allow orders to be updated according to the financial events of the charge.
In case of temporary unavailability between the platforms, updates may occur a few moments after the financial event.
Practical examples
Installment example
A store can configure:
- up to 6 credit card installments;
- different interest rates for each number of installments;
- a minimum amount of R$ 20.00 per installment.
In this scenario, a R$ 100.00 order may display fewer installment options if the configured minimum amount is not reached.
Automatic order update example
Typical flow:
Customer places an order
↓
Payment created in Asaas
↓
Payment confirmed
↓
Webhook automatically sent
↓
Order updated in NuvemshopThis behavior occurs automatically after the module installation.
What are the most common errors?
Invalid API Key
This may occur when the configured key belongs to another account or was entered incorrectly.
Installments unavailable
This may occur when the configured minimum installment amount is greater than allowed for the purchase.
Expired Pix
When the configured expiration period is reached, the order may be canceled.
Payment and order mismatch
In situations of temporary unavailability, the order update may occur a few moments after payment confirmation.
Best practices
Recommended
- Perform test purchases after changing settings.
- Periodically review installment and interest rules.
- Use a valid production account API Key.
- Monitor orders after changes to the module.
- Validate checkout behavior before launching campaigns or handling large sales volumes.
Related content
- Installing the Asaas module for Nuvemshop.
- Initial settings.
- Asaas account configuration.
- Webhooks documentation.
- Available payment methods.
