Payments
Connect your payment provider to see completed payments and refunds in the Revenue dashboard. Matching tracked identities connect payments to their acquisition source.
Connect Stripe
Open Website → Revenue → Settings and choose Connect Stripe. Approve read access to your Stripe account, then return to Databuddy. You do not need to create a webhook or select events for this connection.
The connection receives new payments and imports the 12 months of payments and refunds before you connected, with progress shown in Revenue settings. Browser identity metadata connects payments to visits; older imported payments usually stay unattributed because their visits are no longer available to match. Each Stripe account and environment connects to one website. Payments whose metadata names another website in your organization appear on that website, so one Stripe account can serve several sites. A test-mode connection receives test payments, while a live connection receives live payments.
If Connect Stripe is unavailable in your deployment, use the manual webhook setup below. Paddle also uses that setup.
Add browser identity to your payments
Metadata connects a payment to a tracked visitor. Include the IDs you have: every field is optional, but an ID alone does not prove attribution. Databuddy must find a matching browser event on the same website at or before the payment.
Databuddy first tries the payment's tracked session, then its profile ID, then its anonymous ID. If none matches, it can reuse a previously verified session for the same provider customer on the same website. Ambiguous sessions and sessions belonging to another identified profile are not credited. Stripe invoice context can supply IDs missing from a payment webhook.
Revenue attribution measures attributed completed-payment revenue divided by total completed-payment revenue in the selected currency. Refunds are reported separately. Profile revenue can show a payment associated with a user even when no browser event exists to attribute its acquisition source.
Verify it works
Send a test payment (Stripe test mode works), then check Website → Revenue. The transaction appears within seconds of the webhook delivery. If you passed a profile ID, the revenue also shows on that user in Website → Users.
Troubleshooting
Manual webhook setup
This fallback is for Paddle and deployments without the Stripe App connection. App-connected Stripe accounts use the managed delivery path, so old manual retries cannot overwrite their reconciled payments.
Generate your webhook URL
Add the webhook to your provider
How is this guide?