On this page
No Headings
Last updated: July 28, 2026
Resolve verification failures, bounce issues, and DNS configuration errors. If you run into issues with your custom email domain, use this page to diagnose and resolve common problems.
If your domain hasn't verified after 72 hours, check the following:
acme.com, enter only bounce in the Name field, not bounce.acme.com.PayPal sends your emails from [email protected] instead of your custom domain when a domain health check fails. Common causes include:
In the PayPal dashboard, select Invoicing > Settings > Domain to see the current status and per-record diagnostics. Correct the issue and the system restores custom sending on the next health check cycle.
If a custom-domain email bounces, PayPal's behavior depends on the cause:
| Cause | PayPal behavior |
|---|---|
| SPF, DKIM, or DMARC failure | PayPal automatically attempts to re-verify your domain and retry sending. If your domain is no longer valid, the email falls back to [email protected]. See High bounce rates for more information. |
| Invalid or nonexistent recipient address | PayPal sends a bounce notification to the merchant. |
| Recipient mailbox full | PayPal sends a bounce notification to the merchant. |
For SPF, DKIM, or DMARC failures, your domain status moves to pending while PayPal attempts to re-verify. You'll receive an email notification when this happens. No action is required until PayPal confirms the domain status.
A 5.7.x bounce code indicates a domain authentication failure. Check that your SPF, DKIM, and DMARC records are correctly configured using dnschecker.org or select Verify Domain from Invoicing Settings.
When PayPal detects an authentication failure:
Your domain status moves to pending during re-verification. You'll receive an email notification and no action is required until PayPal confirms the domain status.