PayPal not working usually comes from login trouble, payment method issues, account limits, security flags, or a live outage.
Nothing stalls a checkout like a wallet that refuses to cooperate. This guide groups the main failure types and walks you through fast fixes that restore a smooth pay or withdraw flow. You will see quick checks first, then deeper steps with clear actions that match the most common error messages users meet on web and app.
Why PayPal Stops Working: Fast Checklist
Run through these short checks in order. Many blocks clear in minutes once the right cause is found. If a step fixes the issue, you can stop there.
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| Login loop or no code | Two-step code problem | Try authenticator app codes, new SMS route, or backup method |
| “We couldn’t confirm it’s you” | Risk check on device or IP | Use a trusted device, home Wi-Fi, and the latest app |
| Can’t send or withdraw | Account limitation | Open the Resolution Center tasks and submit asked items |
| Card charged, order failed | Bank authorisation hold | Holds drop back in a few days; try a different method |
| “Payment declined” at checkout | Issuer decline or rule | Call the card bank, then retry or add a fresh card |
| “Something went wrong” errors | Service incident | Check the PayPal Status page and wait for green lights |
| Buyer can’t pay you | Currency, country, or API mismatch | Enable the currency, update seller settings, or use standard checkout |
| App freezes or spins | Cache or old build | Update the app, clear cache, log out and back in |
| Phone lost or number changed | Two-step tied to old phone | Use Help Center flow for number change and regain access |
Check Service Status And Outages
Before long troubleshooting, confirm it isn’t a wider incident. Open the PayPal Status page. If payments or login show a red or amber notice, retry after the listed window. When the page shows green, move to the next step.
Confirm You Can Access The Account
If codes never arrive or the app rejects a correct password, the two-step layer may be the blocker. Open the authenticator app and enter a live code, not a stored one. If SMS is slow, move to voice call where offered. After a number change, use the “changed my mobile” Help Center path to regain entry and refresh two-step on the new phone.
Clear Account Limits And Holds
When sending or withdrawing fails with a banner about limits, you need to finish listed tasks. Open the Resolution Center and upload the exact items asked. That can include ID, proof of address, or supplier invoices for sellers. Once checks pass, limits lift and normal use resumes. Learn more about removing a limit in the PayPal help article on account limitation.
Fix Login And Security Hiccups
Two-Step Codes Fail
Time drift breaks codes. Sync time on your phone, then create a fresh code. If you rely on SMS, try a location with strong signal, toggle airplane mode off and on, then request a new code. Many users keep both app codes and SMS active to avoid a single point of failure.
Changed Phone Number
Lost access to the old number? Use the Help Center flow for a changed mobile. After login is restored, add two methods: an authenticator app plus a backup code set. Store backups in a safe place offline.
“We Need More Info” Prompts
Those prompts appear when risk checks need extra proof. Follow the on-screen steps and provide clear photos or PDFs. Keep file sizes within the upload limit and match names to the account profile.
Payment Fails At Checkout
When a merchant page returns a generic decline, the card bank often blocked the try. A quick call to the bank clears many cases in minutes. After the bank unblocks, re-add the card inside Wallet and run a small test payment before a large one.
Card Or Bank Declines
New cards, travel, or mismatched billing details trigger filters. Match the name and address to the bank record exactly, use the same country across shipping and billing, and retry from a stable IP. If a merchant still rejects the wallet, pay with a different card or your balance and follow up with the bank for the root cause.
Authorisation Holds Look Like Charges
When a payment fails, the issuer may leave a temporary hold. The hold falls away after the bank’s window. If the funds do not return on the expected day, call the bank and reference the hold ID in your activity view.
Insufficient Funds Or Spend Caps
Linked bank accounts can have low daily caps. Cards also have per-day limits. Split a large buy into smaller parts, add a second card, or move funds into the wallet first.
Name, Address, And Currency Mismatches
Mismatches spike declines. Use one language and script for names, match street lines to the bank record, and pick the same currency as the card’s native currency when you can. If you must convert, review the rate before you hit pay.
Seller Settings That Block Buyers
Sellers can add filters that block certain countries, currencies, or card types. If buyers from a region report the same failure, loosen the filter or enable the missing currency. For API flows, match the order total sent at the start and at the final capture. Widely seen API errors include 10417 when the wallet cannot fund the order under the bank’s rules.
Device, App, And Browser Fixes
Out-of-date apps or a cluttered browser trip up login and pay flows. Update to the latest build, clear cache and cookies, and try a private window. Move off public Wi-Fi, avoid VPNs, and switch to mobile data or home broadband. On desktop, disable aggressive content blockers for the pay page, reload, and try again.
Withdrawals And Holds
New accounts, sudden spikes in sales, or risk alerts can place money on a short hold. Check the date next to the pending amount to see when the money will release. Upload tracking on shipped orders, respond to disputes fast, and keep chargebacks low to shorten hold time over the next cycles.
Second Table: Error Codes And Messages
| Error Or Message | Meaning | Action |
|---|---|---|
| 10417 | Wallet cannot fund order | Offer other methods or lower the amount, then retry |
| “Payment declined” | Issuer blocked the try | Ask the bank to allow the charge, then re-add the card |
| “We couldn’t confirm it’s you” | Risk checks need more proof | Use a trusted device and finish any ID prompts |
| “Payment pending” | Risk or seller review in progress | Wait for the date shown or contact the seller |
| “You can’t send money right now” | Limit or compliance task | Open Resolution Center and finish listed steps |
| “Something went wrong” | Service issue or bad cache | Check status page, update the app, and retry |
Merchant Tips That Solve Buyer Failures
Match Amounts Across API Calls
Keep the amount sent in the first call close to the final capture. A large jump triggers risk filters and raises 10417 odds. Send taxes and shipping in the first step when you can.
Enable The Right Funding Sources
Turn on card payments through the wallet, enable local methods where you sell, and allow guest checkout if it fits your risk level. Offer a card form as a fallback so buyers can still pay when the wallet stalls.
Keep Disputes Low
Ship on time, upload tracking, and answer buyer messages with clarity. A run of claims can trigger new checks that slow payouts. Clean post-sale practice keeps funds flowing.
When To Reach The Help Team
If nothing here clears the block, use the Help Center paths tied to your banner or message. For limits, open the case and send each item exactly as asked. For login, use the changed mobile path or the authenticator app route. For outages, subscribe to email alerts on the status page so you hear when incidents end.
FAQ-Free Bottom Line
Wallet trouble tends to come from five buckets: login, limits, payment method rules, seller filters, and live incidents. Start with status, move to account access, clear limits, fix the card or bank side, and review seller settings. With those steps, most users restore pay and withdraw flows without a long wait.