Payment gateway showing as a referral in GA4 (Stripe, PayPal, Klarna)
If your checkout sends customers off to Stripe, PayPal or Klarna to pay and then back to a thank-you page, GA4 often credits the sale to the payment provider instead of the real source. Your best campaigns lose their conversions to "paypal.com".
Why it happens
When the customer leaves your site to pay and returns, GA4 sees the return as a new referral from the payment provider's domain. That starts a new session attributed to, say, stripe.com, and the purchase gets credited there, stealing it from the Google, Meta or email campaign that actually drove it. It is the same mechanism as a self-referral, just from a third party.
How to confirm it
Look at your traffic sources or conversion paths for referrals from stripe.com, paypal.com, checkout.klarna.com and similar. If those domains are credited with conversions, this is your problem.
How to fix it
- Add each payment domain to your referral exclusion list in GA4 (Admin, data stream, configure tag settings, list unwanted referrals), so a return from them does not start a new session.
- For a checkout that spans domains, set up cross-domain tracking so the session and its original source carry through the payment step.
Once excluded, the conversion flows back to the campaign that earned it, and your channel reports start telling the truth again.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Self-referrals in GA4