FAQ - Nuvemshop

Frequently asked questions about the Nuvemshop module

See the main questions about payments, limitations, and synchronization in the integration between Asaas and Nuvemshop.

To install or change the module settings, use the specific guides indicated in the answers.

Which payment methods are supported?

The integration lets you receive by:

  • Pix;
  • bank slip (boleto);
  • credit card, single payment;
  • credit card in installments.

Debit card is not supported.

Can I use the Sandbox?

No.

The Nuvemshop integration uses only an Asaas Production account.

🚧

Attention

Since there is no Sandbox support, we recommend using low amounts and making controlled test purchases before making the store available to customers.

Can I offer installments and apply interest?

Yes.

Installments are available only for credit card.

When configuring the module, you can define:

  • maximum number of installments;
  • interest for each number of installments;
  • minimum amount per installment.
📘

Important

The minimum amount per installment may also limit the number of installments available for certain purchases.

If a purchase does not reach the configured minimum amount, the checkout may display fewer installments than the defined maximum limit.

See Initial settings to review these rules.

Can I configure subscriptions or recurring charges?

Not through the Nuvemshop integration.

The Asaas module for Nuvemshop does not support recurring charges.

If your operation needs to generate charges periodically, see Subscriptions in Asaas.

How are orders updated after payment?

The communication between Asaas and Nuvemshop is configured automatically during module installation.

Payment changes are sent via Webhooks so that the corresponding order is updated in Nuvemshop.

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
A["Customer makes the purchase"] --> B["Payment is created in Asaas"]
B --> C["Payment is updated"]
C --> D["Asaas sends the Webhook"]
D --> E["Order is updated in Nuvemshop"]

classDef inicio fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:3px
classDef validacao fill:#E0F2FE,stroke:#0284C7,color:#0C4A6E,stroke-width:2px
classDef sucesso fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:3px

class A inicio
class B,C,D validacao
class E sucesso

linkStyle default stroke:#94A3B8,stroke-width:2px

Synchronization is automatic. You do not need to implement periodic API queries to track orders created by the module.

The order was not updated after payment. What should I check?

In cases of temporary unavailability between the platforms, the update may occur a few moments after the payment changes.

If the discrepancy persists:

  1. confirm that the charge was updated in the Asaas account connected to the module;
  2. validate that the integration is still active in Nuvemshop;
  3. confirm that the configured API Key is still valid.

Avoid changing the order manually before confirming whether synchronization is still being processed.

Why did the Pix become unavailable?

The Pix may expire according to the period defined in the module configuration.

When the configured period is reached, the payment is no longer available and the order may be canceled.

Review the expiration period in Installing the module.

Why are installments not available?

Check:

  • the total purchase amount;
  • the configured maximum number of installments;
  • the minimum amount allowed per installment.

The minimum amount may reduce the number of installments displayed or prevent installments for a given purchase.

What should I check if the API Key is rejected?

Confirm that:

  • the key was copied in full;
  • the key is still active;
  • the credential belongs to the Asaas account connected to the store;
  • the key is a Production key.

If necessary, create a new API Key and update the installation.

See Installing the module.

📘

Recommended

  • Make test purchases after configuration changes.
  • Periodically review the installment and interest rules.
  • Use a valid API Key from the production account.
  • Monitor orders after changes to the module.
  • Validate the checkout behavior before starting campaigns or high sales volumes.

Next steps


Did this page help you?