When a customer doesn't receive a payment receipt, two things happen. First, they wonder if the charge actually went through and sometimes pay again. Second, when they see the line on their statement two weeks later, they don't recognize it and file a chargeback. Both outcomes are expensive. Both are largely a function of which payment processor sent the receipt.
Stripe receipts inbox at 99%+ when sent from your own domain via their custom-sender option. PayPal receipts sit at around 95% but frequently land in Promotions. Square's deliverability varies significantly by region. If receipts matter to your business — and they do — choose the processor on email behaviour, not just checkout UX.
Stripe: own-domain receipts, near-perfect inbox
Stripe's default receipt sends from receipts@stripe.com, which has a strong sender reputation built up over a decade. Inbox placement on the default sender is consistently above 98% at Gmail, Outlook 365, and Yahoo. The receipts are short, well-formatted, and almost always tagged for the Updates or Primary tab in Gmail.
For merchants who care about brand consistency, Stripe also offers custom-domain receipts: the receipt is sent from your own domain (configured via billing.yourdomain.com with proper DKIM and SPF) and signed by Stripe's infrastructure. Setup takes 10 minutes if your DNS is in order. Once configured, Stripe handles the SPF and DKIM keys automatically and you inherit the deliverability characteristics of your own domain's reputation.
The catch: if your domain's reputation is weak, custom-domain receipts can underperform the default. For a new SaaS without strong domain history, stay on the Stripe-domain default until your own domain is warmed up.
PayPal: paypal.com sender, mixed placement
PayPal sends all transactional mail from paypal.com domains. The reputation is strong by virtue of volume — PayPal is one of the top transactional senders in the world — but placement is less consistent than Stripe's. Specifically:
- Gmail: roughly 95% inbox, but a meaningful share lands in Promotions rather than Primary, especially for "Send money" notifications and refund confirmations.
- Outlook 365: 96-98% inbox.
- Yahoo: 93-96% inbox, with a measurable spam rate.
- ProtonMail / Tutanota: reliable inbox, but the heavy HTML template can render poorly.
The structural problem with PayPal: you cannot configure the sender. It's always paypal.com. So the deliverability you get is the deliverability you get. For high-volume businesses where receipt deliverability drives chargeback rate, this is a real constraint.
Square: regional variance
Square sends from squareup.com. North American deliverability is solid (95%+ inbox at major providers). Outside North America, Square's sender reputation is weaker, and placement degrades — particularly at European providers like Orange.fr, T-Online, and at Russian/CIS providers like Mail.ru and Yandex.
For a US merchant whose customers are exclusively domestic, Square is fine. For a merchant serving European customers, Square's receipt deliverability becomes a real concern, and the response repertoire is limited because Square doesn't offer custom- domain receipts in the same way Stripe does.
White-label and own-sender alternatives
For merchants who want full control of receipt deliverability, the options are:
- Stripe custom-domain receipts. The simplest path. Stripe handles authentication on your subdomain.
- Disable processor receipts, send your own. Turn off the Stripe/PayPal/Square receipt and send your own from your transactional ESP (Postmark, SparkPost, SES). You control the template, the sender, the domain reputation.
- Both — receipt + your own confirmation. Risky. Customers get two emails for one charge, doubling the chance one lands in spam and increasing complaint rate. Avoid unless you have a specific reason.
For most operators above $50k MRR, sending your own receipts is the right answer. The control over template, branding, and especially deliverability is worth the engineering work.
Whatever processor you use, a receipt with the merchant name in the subject line and a recognizable amount in the first body line gets opened, gets remembered, and reduces the unrecognized-charge chargeback rate by double-digit percentages. Mystery merchant names on credit-card statements are the leading cause of friendly-fraud chargebacks.
How to test receipt deliverability across processors
Cross-testing receipt deliverability is straightforward but rarely done. The methodology:
- Set up seed inboxes at Gmail, Outlook 365, Yahoo, Apple iCloud, and a regional provider relevant to your audience.
- Run a real test charge for each processor you're evaluating, targeting each seed.
- Record placement (Inbox, Promotions, Spam, missing) and any warnings or icons applied by the client.
- Repeat monthly to catch reputation shifts.
The data this produces will surprise you. Receipt deliverability is often the difference between a 0.6% chargeback rate and a 1.4% chargeback rate at the same merchant.
Recommendation by business type
- SaaS with own brand: Stripe custom-domain receipts.
- Marketplace with multi-merchant invoicing: Stripe Connect with platform-branded receipts.
- Local commerce in North America: Square is fine.
- EU SaaS or commerce: Stripe over PayPal where possible; if PayPal is required, send your own confirmation in addition.
- High-volume subscription: Send your own receipts via Postmark or equivalent. Disable processor-side receipts.