Connect PayPal to Nevian

Time needed: about 10 minutesLast updated:

Connect PayPal 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 PayPal 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 PayPal and click Next with the platform open in another tab.

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

    Drawing: Connect PayPal. Webhook URL: https://track.example.com/wh/paypal/••••••••; Webhook ID: Required account fields are saved with Next

  3. In the PayPal Developer Dashboard, switch to Live, open Apps & Credentials, choose the REST application your checkout uses, then Live Webhooks → Add Webhook.

    Drawing: PayPal · webhook configuration. Apps & Credentials: Your checkout application; Live Webhooks: Add Webhook; Webhook URL: Paste the Nevian URL

  4. Paste the URL, subscribe to the events below and save. Copy the displayed Webhook ID into Nevian; it is required for signature verification, even though it is not a password.

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

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

    Drawing: Connect PayPal. Webhook ID: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Use a real sandbox-app order with a separate source and sandbox Webhook ID. The generic Webhooks simulator signs for a placeholder ID and is rejected by this prepared connection. Back in Nevian, look for Connected, then click Done.

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

Events: CHECKOUT.ORDER.APPROVED, CHECKOUT.PAYMENT-APPROVAL.REVERSED, PAYMENT.CAPTURE.COMPLETED, PAYMENT.CAPTURE.PENDING, PAYMENT.CAPTURE.DENIED, PAYMENT.CAPTURE.DECLINED, PAYMENT.CAPTURE.REFUNDED, PAYMENT.CAPTURE.REVERSED and CUSTOMER.DISPUTE.CREATED. Buyer approval alone is pending; the captured payment creates the sale.

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.
  • Set the purchase unit’s custom_id to the visit ID when creating the order. The source and webhook must belong to the app used by the checkout; another app’s webhook cannot observe its transactions.

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.