Connect Pagar.me to Nevian

Time needed: about 10 minutesLast updated:

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

What you need

  • A Pagar.me 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 Pagar.me and click Next with the platform open in another tab.

    Drawing: Connect Pagar.me. 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 Pagar.me.

    Drawing: Connect Pagar.me. Webhook URL: https://track.example.com/wh/pagarme/••••••••; Connection: Keep the complete URL, including its private key

  3. In Pagar.me, open Conta → Configurações → Webhooks and create a webhook for your v5 account.

    Drawing: Pagar.me · webhook configuration. Conta: Configurações → Webhooks; URL: Paste the Nevian URL; Authentication: Leave optional HTTP authentication off

  4. Paste the URL, select the events below and save. Leave optional HTTP authentication disabled: the private key in the URL authenticates this connection.

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

  5. Return to Nevian and click Next to open the connection test.

    Drawing: Connect Pagar.me. Setup: Webhook URL copied; 3 · Test: Waiting for the first event…

  6. Send a controlled order from a separate test workspace. This adapter does not infer test mode from Pagar.me credentials; keep pixels in test mode before sending sample orders. Back in Nevian, look for Connected, then click Done.

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

Events: order.created, order.paid, order.payment_failed, order.canceled, charge.refunded, charge.partial_canceled and charge.chargedback. For subscriptions also use invoice.paid, invoice.payment_failed and invoice.canceled. Partial refunds are logged; only a full refund changes the sale to refunded. Subscription charges are tracked, but this connection does not calculate MRR.

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.
  • Your server must put the visit ID in metadata.btk when creating the order or subscription. A per-visitor payment link can use order_code; a shared link cannot carry a different click ID for each buyer.

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.