Connect PagBank to Nevian

Time needed: about 10 minutesLast updated:

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

What you need

Availability. This connection is not available in this version of the panel yet. Use this guide to prepare the account settings; continue only when its named integration and credential fields appear in your workspace. Do not send its events to Custom or another provider URL.

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

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

    Drawing: Connect PagBank. Webhook URL: https://track.example.com/wh/pagbank/••••••••; PagBank API token: Required account fields are saved with Next

  3. On the PagBank account website, open Vendas → Integrações → Gerar token. The token and the account email are required in Nevian when this connection becomes available.

    Drawing: PagBank · webhook configuration. Vendas: Integrações; Token: Keep in Nevian integration settings; Account email: The email of the PagBank account

  4. For Orders API requests, put the URL in notification_urls. For hosted checkouts, use payment_notification_urls: checkout notification_urls alone describes checkout status, not the payment.

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

  5. Return to Nevian, enter PagBank API token and click Next to save it before sending an event. Copy it from the same account and webhook you just configured.

    Drawing: Connect PagBank. PagBank API token: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Use a sandbox order with its own sandbox token and a separate source. The prepared integration recognizes sandbox orders as tests; legacy notification-code-only sales are logged without creating a purchase. Back in Nevian, look for Connected, then click Done.

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

The account email is needed for the notification API. This guide does not create any new storage for personal data. Do not configure credentials until the matching fields are available in your workspace.

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.
  • For orders, put the visit ID in metadata.btk and use the same unique reference_id for order and charge. For hosted checkouts, use the visit ID or btk=<click ID> in reference_id.

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.