Many users suddenly find that PayPal is not working for online checkout or sending money, leaving payments stuck and accounts locked. This guide walks through the most common causes and clear steps to restore full functionality quickly.
Below is a structured overview of why transactions fail, how account restrictions appear, and which settings or regional factors usually create the disruption.
| Failure Category | Likely Cause | Quick Indicator | Immediate Action |
|---|---|---|---|
| Payment Declined | Card issuer or funding source block | Error code in checkout page | Contact bank or try another method |
| Hold or Restriction | Risk rules, new login, or compliance flag | Account badge shows hold | Upload documents in Resolution Center |
| Transfer Failure | Invalid bank details or daily limits | Status remains pending or returned | Verify account numbers and increase limits |
| Integration Issues | Broken API keys or webhooks | Developer logs show errors | Validate webhook endpoints and credentials |
Payment Declines on Checkout
When PayPal is not working at checkout, the payment often fails because of card issuer rules, regional blocks, or mismatched billing details. Merchants see higher abandonment when currency, address verification, or 3D Secure challenges interrupt the flow.
Browsers with strict privacy extensions can block the PayPal JavaScript, which makes the button invisible or nonresponsive. Clearing cache, disabling ad blockers, and testing in an incognito window usually reveals whether the problem is technical interference rather than account limits.
Each decline includes an error code that maps to a specific action, such as update card details, retry later, or contact support. Keeping a record of these codes helps customer service resolve escalations much faster.
Account Holds and Restrictions
PayPal may freeze limited features when risk engines detect unusual activity, such as a login from a new device or a sudden change in transaction volume. These holds protect both the platform and users, but they temporarily make it seem like PayPal is not working for sending or receiving.
Resolution Center requests documents like ID, invoices, or bank statements to verify identity and transaction legitimacy. Responding with clear, high-quality files reduces manual review time and brings the account back to normal status sooner.
Merchants with business accounts must maintain consistent legal names, tax information, and accurate product descriptions across listings. Sudden changes in these fields often trigger compliance reviews that appear as functionality outages to the user.
Transfer and Withdrawal Problems
Transfers that stay pending or return to sender usually trace back to invalid bank details, mismatched names, or exceeded daily or monthly withdrawal limits. Before resending funds, confirm the full routing and account number exactly as shown on the external bank form.
Regional regulations such as sanctions lists or enhanced due diligence can delay payouts to certain countries. Verifying source of funds and providing additional documents satisfies compliance requirements and unblocks stalled transfers.
Currency conversion fees, local banking cutoffs, and incorrect intermediary details create additional friction in cross-border payouts. Reviewing the fee summary and supported corridors in the profile settings prevents surprises and repeated failed transfers.
Developer and Integration Failures
For platforms and SaaS tools, PayPal is not working when webhooks do not fire or API calls return unauthorized errors. Rotated secrets, expired tokens, and IPN listener failures break order fulfillment and confuse support teams.
Sandbox testing with realistic payloads confirms that webhook endpoints accept traffic and respond with correct acknowledgments. Checking application logs for timeout errors and mismatched webhook IDs isolates integration faults quickly.
Upgraded API versions, scopes, and merchant references must align between client code and the developer dashboard. Synchronizing SDK libraries and refreshing credentials ensures that new features work as expected without legacy breakage.
Key Actions to Restore PayPal Functionality
- Check browser console and network logs for JavaScript or webhook errors
- Verify funding sources, bank details, and currency compatibility
- Respond promptly to document requests in the Resolution Center
- Test payments in sandbox and production modes before going live
- Keep error codes and timestamps to speed up support resolution
FAQ
Reader questions
Why does PayPal say my payment was rejected even though my card balance is sufficient?
The card issuer or PayPal risk rules may have declined the transaction based on spending patterns, currency limits, or mismatched billing address, so the block is at the authorization stage rather than the balance level.
My transfer to my bank shows pending for days, why is PayPal not working for withdrawals?
Daily limits, compliance reviews, or unverified bank details keep the transfer in pending; verify your identity in the Resolution Center and confirm the exact account numbers to clear the queue.
PayPal button not showing on my online store, is the account frozen?
Often the button is hidden because of JavaScript errors, ad blockers, or mismatched integration keys; validating webhook endpoints and SDK versions usually restores the checkout flow without an account freeze.
What should I do if I receive an error code during checkout?
Record the exact code, cross-check it with PayPal documentation, retry with an alternate payment method, and share the code with support so they can pinpoint whether it is a card, currency, or restriction issue.