Connect Asaas to Nevian

Time needed: about 10 minutesLast updated:

Connect Asaas so sales and payment changes reach Nevian and can be matched to the visit that brought the buyer.

What you need

  • A Asaas account with permission to configure notifications.
  • An active Nevian plan and an owner, admin or member role. Viewers cannot connect integrations.
  • Keep the checkout and Nevian tabs open side by side.

Steps

  1. In Nevian, open Integrations → Add integration (Connect provider in an empty workspace), choose Asaas and click Next with the platform open in another tab.

    Drawing: Connect Asaas. 1 · Open platform: Have your account open in another tab; 2 · Copy the URL: Next creates your private connection URL

  2. Copy the complete Webhook URL. Keep it private and leave this window open while you configure Asaas.

    Drawing: Connect Asaas. Webhook URL: https://track.example.com/wh/asaas/••••••••; Webhook Auth Token: Required account fields are saved with Next

  3. In Asaas, open Menu do usuário → Integrações → Webhooks → Criar Webhook.

    Drawing: Asaas · webhook configuration. Nome: Nevian payments; URL: Paste the Nevian URL; Auth Token: Generate a token for this webhook

  4. Enter a name and URL, generate an Auth Token, enable delivery and select the payment events below. Use a dedicated webhook token, not your API key.

    Drawing: Asaas · delivery settings. Destination: Your private Nevian Webhook URL; Scope: The products and events described in this step

  5. Return to Nevian, if you use the optional token, enter Webhook Auth Token and click Next to save it before sending an event. Use the same value configured for this webhook; for a token you generate yourself, use that exact value in both places. Leave an optional token empty in both places if you do not use it.

    Drawing: Connect Asaas. Webhook Auth Token: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Send a sandbox payment to a separate test workspace with pixels already in test mode. This connection does not infer a test conversion from Asaas sandbox delivery alone. Back in Nevian, look for Connected, then click Done.

    Drawing: Connect Asaas. Connection: Connected; Last event: Received just now

Select PAYMENT_CREATED, PAYMENT_CONFIRMED, PAYMENT_RECEIVED, PAYMENT_OVERDUE, PAYMENT_DELETED, PAYMENT_REFUNDED, PAYMENT_PARTIALLY_REFUNDED, PAYMENT_REFUND_IN_PROGRESS, PAYMENT_CHARGEBACK_REQUESTED, PAYMENT_CHARGEBACK_DISPUTE, PAYMENT_AWAITING_RISK_ANALYSIS, PAYMENT_REPROVED_BY_RISK_ANALYSIS and PAYMENT_CREDIT_CARD_CAPTURE_REFUSED. Subscription payments do not calculate MRR here.

Check that it works

  • Open Logs → Webhooks and confirm the provider, order ID, event and result. A delivered webhook can be logged without creating a sale when the event is informational.
  • When your server creates a charge, put the visit ID in externalReference, either alone or as btk=<click ID>. Asaas payment events have no buyer email for fallback matching; shared payment links can remain unattributed.

Problems

Waiting for the first event…

Check the complete URL, event subscriptions and product scope. If you rotated the integration key, replace the URL in the provider too.

The call was rejected

Read the reason in Logs → Webhooks. Check the secret when one is configured, then resend the original event after fixing the configuration.

No matching click

Check the click ID instructions above on a real ad visit. A provider test usually has no ad click; that alone does not mean delivery failed.

Still stuck? Write to [email protected].

Images are our own drawings and configuration diagrams, not screenshots. Use the current values from your account; the examples contain no live credentials.