Orders paid for but never marked paid
PayPal collected the money and tried to tell the store, the store's listener threw an error, and the retry queue gave up before anyone noticed.
Every payment lands in the order
Working with PayPal?
Most PayPal problems that reach us are not really about cards being declined. The buyer paid, PayPal says the money moved, and the store never heard about it. We find where the notification went and we make sure the next one lands.
What it is
PayPal Holdings, Inc. (NASDAQ: PYPL) is an online payment platform used by roughly 435 million active accounts worldwide. It was founded in 1998 out of Confinity and X.com, became part of eBay in 2002, and was spun back out as an independent public company in 2015.
Its product range covers Checkout buttons and smart checkout, Payouts, Subscriptions, Braintree (acquired in 2013), Venmo and Pay Later. Two API families live side by side: the older Classic stack built on NVP or SOAP with IPN for notifications, and the modern REST stack built on Orders v2 with Webhooks. The two do not share credentials, event shapes or verification flow, which is where a lot of the pain starts.
The honest version
No technology is all upside. This is where PayPal earns its place and where it tends to cause trouble.
Sound familiar?
The PayPal problems that bring people to us, and what you have once each one is fixed.
PayPal collected the money and tried to tell the store, the store's listener threw an error, and the retry queue gave up before anyone noticed.
Every payment lands in the order
A webhook signed under one app ID is being verified against another, usually after a copy-paste from sandbox to live.
Verified against the right app
Smart checkout returning a decline for cards that work elsewhere, often down to AVS, 3-D Secure or a seller-protection rule set too tight.
Legitimate orders go through
A risk review has locked the account and withdrawals are blocked until paperwork is submitted and accepted.
Documents in, limitation lifted
Billing agreements cancel themselves after repeated funding failures and the customer is never prompted to update.
Dunning that reaches the buyer
The money has already been moved to the bank, so there is nothing left in the PayPal balance to send back.
Refund logic that tops up first
The REST app was created before the scopes it now needs existed, and nobody updated the app's permissions.
Scopes granted, token refreshed
A legacy integration that relies on IPN and hosted buttons, which works today but is on borrowed time.
Moved onto Orders v2 cleanly
What we do
Call us for one failed webhook, or hand us the whole integration.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
The common reasons are a listener URL that now returns a 5xx or a redirect, TLS that PayPal will not negotiate any more, a firewall blocking PayPal's address ranges, or an IPN that is being sent to a sandbox endpoint while the payments are live. We replay the queue from the PayPal dashboard once the listener is answering correctly again.
Most often it is a risk review triggered by a change in volume, a spike in disputes, or a mismatch between what the account was registered for and what is actually being sold. The balance usually releases once PayPal has the documents they ask for, and we help put that package together.
Yes. We stand up a REST app alongside the existing integration, mirror events into both for a period so nothing is lost, then cut the store over once the new path has handled real orders cleanly. Existing subscriptions keep running throughout.
The two processors need separate order states and separate webhook listeners, with the order record holding which one owns the payment. Done that way they coexist cleanly and refunds always go back to the processor that took the money.
Usually the funding source in the buyer's PayPal wallet has expired or been removed, and the billing agreement has been retrying quietly. We turn on dunning emails from PayPal, surface the problem inside your own account area, and give the customer a way to update without starting a brand new subscription.
Estimates are free. Share the merchant account details and the exact failure you see, and we come back with a scope before anything is touched.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: