Help for owners
The PayPal button disappeared from my checkout page
Short answer
The PayPal button is drawn by PayPal's script using your client ID and settings, and it only shows when PayPal reports the payment method as eligible. A changed client ID, a domain that no longer matches, or an eligibility change can hide it. Check the browser's error message and what changed on the page.
Does this sound like your situation?
- The button was there yesterday and the space is empty now.
- It shows on some pages, devices or countries but not others.
- A different PayPal option, such as Pay Later, vanished.
- The button appears but clicking it shows an error.
- It stopped after a site update, plugin update or domain change.
Why does this happen?
The script needs valid settings
In PayPal's current JavaScript SDK you create an instance with your client ID and the components you want, such as payments or card fields. The reference lists runtime errors including ERR_INVALID_CLIENT_TOKEN, meaning the token is invalid or expired.
Confirmed by developer.paypal.com
The domain has to match
ERR_DOMAIN_MISMATCH means the domain does not match the token. A move to a new domain, a staging address or a changed web address can trigger it.
Confirmed by developer.paypal.com
A button should show only when eligible
PayPal's reference says to call an eligibility check for methods such as paypal, venmo, paylater, credit and advanced cards, and to show a button only when it returns true. If it is false, a correct page can show nothing.
Confirmed by developer.paypal.com
Currency, amount and country feed eligibility
The reference says currency defaults when omitted, the amount affects Pay Later thresholds, and the buyer's country is detected if you omit it. A cart or country change can therefore turn an option off.
Confirmed by developer.paypal.com
An order can fail after the button shows
When creating the order, PayPal can answer with errors such as PAYMENT_DENIED or PAYMENT_SOURCE_DECLINED_BY_PROCESSOR, or INSTRUMENT_DECLINED, which stop the payment even though the button loaded.
Confirmed by developer.paypal.com
What can I do about it today?
- Note exactly what you seeIs the button missing everywhere, only on one page, device or country, or does it show an error? Take a screenshot with the page address.
- Ask what changedFind out whether the theme, a plugin, the domain, the checkout page or PayPal's credentials were changed on that date.
- Test another browser or a phoneThis shows whether it is your own browser, an ad blocker or the site.
- Keep another way to pay openIf you can, leave card payment or bank transfer available while this is fixed.
- Do not paste your PayPal secret into chat or emailYour developer needs the client ID for the right app, not your login password.
- Send your developer the browser console messagePress F12, open Console, and copy the red error. It usually names the cause.
When should I bring someone in?
- The button is missing on the live site and you take payments through it.
- You see an invalid token or domain mismatch message.
- Nobody knows which PayPal app or credentials the site uses.
How do I handle it?
- Reproduce and read the errorI load the page, read the console and network responses and find which step fails: script, token, eligibility or order creation.
- Check credentials and domainI compare the client ID and domain on the page with the PayPal app settings.
- Check eligibility inputsI look at the currency, amount and country the page sends, using PayPal's reference.
- Fix and test in a sandboxI make the fix in a PayPal sandbox first, with a small test order.
- Release with a way backThe change goes live with a tested rollback and a note on what the settings must be.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why does it show for me and not my customers?
Eligibility can depend on country, amount and currency, so the button can appear for one buyer and not another.
Is it a PayPal outage?
It can be, but check the error in the browser first. An invalid token or domain mismatch is a settings problem on your side.
Will it come back by itself?
If the cause is a setting or a page change, no. It needs the setting corrected.
Can I just add it again with a plugin?
Find the cause first. Adding another copy of the button code without knowing why the first one stopped can hide the real problem.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.