Webhook notifications are being rejected
The HMAC key rotated in the Customer Area but not in your handler, or two environments share a webhook endpoint and the handler is validating against the wrong key.
Notifications verified and accepted
Running on Adyen?
Adyen is one of the better enterprise processors once it is wired up correctly, and genuinely painful when it is not. 3D Secure 2 flows that silently fall back to a frictional challenge, Drop-in rejecting a payment method that the backend thought was enabled, webhooks retrying for days against the wrong signing key. We work through the integration, tighten the configuration, and leave you with payments that clear without a weekly firefight.
What it is
Adyen is a Dutch-headquartered global payments platform used by many enterprise retailers, marketplaces and in-person merchants. It handles card schemes, local methods across dozens of countries, in-person terminals, payouts, risk management and payment orchestration from a single integration.
The company was founded in 2006, listed on Euronext Amsterdam in 2018, and runs its own acquiring licenses in most major regions, which means fewer intermediaries between you and the card networks. The platform is strongest for merchants with international traffic and genuine scale; it is overkill for a small US-only online shop.
The honest version
No technology is all upside. This is where Adyen earns its place and where it tends to cause trouble.
Sound familiar?
The Adyen problems that bring people to us, and what you have once each one is fixed.
The HMAC key rotated in the Customer Area but not in your handler, or two environments share a webhook endpoint and the handler is validating against the wrong key.
Notifications verified and accepted
The fingerprint step times out, the issuer forces a challenge, and what should have been a frictionless authentication turns into a challenge the shopper abandons. We trace it through the auth response and tune the risk signals sent.
3DS2 as frictionless as the issuer allows
The payment method is enabled in the Customer Area for one country but the shopper's country does not match, or the merchant account on the API key does not carry the method.
Methods present for every country you sell in
The initial payment did not store a shopperReference and recurringProcessingModel, so the renewal has nothing to act against and returns a generic refusal.
Recurring contracts stored on first charge
EEA transactions that are not SCA exempted and did not complete authentication get refused by the issuer. Exemptions, delegated authentication and the right 3DS flow all need tuning per region.
SCA handled per region
A dispute arrived on a transaction where 3DS was not used, so the liability shift that would have put the loss on the issuer never kicked in. The chargeback lands on the merchant.
Dispute posture that reflects the auth
A rotation that was not coordinated with every service holding the key, or a key scoped to one merchant account being used against another. Payments fail with the same error everyone else sees.
Key rotations tracked end to end
What we do
Call us for one failing 3DS flow, or let us own the Adyen integration alongside your payments team.
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 causes are 3DS2 flows falling back to challenge in regions where frictionless was previously working, risk rules tightened without a corresponding retry path, and local payment methods that are not configured for the shopper's country. We pull the refusal reasons from the last month, split them by region and issuer, and give you a short list of specific fixes rather than a general audit.
Verify the HMAC signature on every notification, return 2xx within a few seconds, and process asynchronously on your side. Store the pspReference and treat duplicates as idempotent. Adyen will retry for days against a failing endpoint, which is good when your endpoint recovers and bad when the endpoint is misbehaving.
Only if you are at a scale where the approval rate difference, the local payment method breadth and the interchange plus pricing matter more than Stripe's developer experience. For a US-only mid-market shop the answer is often no. For a global enterprise with physical stores and recurring revenue, Adyen frequently wins on numbers. We compare for your actual traffic rather than the generic answer.
3DS2 under SCA is strict. Missing device fingerprint data, challenge windows the checkout was not designed to render, and transactions that qualified for an exemption but did not request one are the top three reasons. Each shows up as a different refusal reason, and the fix is specific per cause.
Yes, through recurring contracts. The gotcha is that the initial payment must store a shopperReference and the right recurringProcessingModel, otherwise later charges have nothing to anchor to. Teams that bolted subscriptions onto an existing one-shot integration run into this on the second month.
Nothing for a quote. Share the account structure, the refusal pattern and the countries you sell in, and we return a figure before any work begins.
Free estimate
Send us the merchant accounts, the refusal breakdown and where the integration is failing. A real 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: