← Back to all articles

Stripe vs PayPal: How Payment Gateways Verify Merchant and Customer Addresses

Stripe and PayPal both verify addresses, but they do it at different moments and for different reasons. Understanding the split helps you predict when a user will be asked for an address — and what will happen if it does not match.

Merchant onboarding (KYC)

Stripe collects a legal entity and a physical address during onboarding and may request documents later. PayPal does the same for business accounts and, depending on jurisdiction, for personal accounts with high balances. In both cases, a real, verifiable address is the baseline — a PO Box often is not accepted for entity registration.

Customer-facing verification

At checkout, Stripe lets the merchant choose how strictly to apply AVS and CVC checks via its Radar rules. PayPal, by contrast, rarely shows AVS-style declines to the buyer — the buyer authenticates with their PayPal login, and address risk is handled inside PayPal's own network. That is a meaningful difference: PayPal shifts address risk onto itself, while Stripe surfaces it to you.

Why it matters when you integrate

When building or testing an integration, exercise the address fields realistically. A test card with a nonsense address will not behave the same as a real checkout, and you will miss the decline and review flows that actually cost you money in production.