Running on Adyen?

Adyen 3DS or webhooks giving you grief? We ship it properly.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

adyen-notifications.log

noisy

What it is

Adyen at a glance

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.

Type
Enterprise global payments platform
First released
2006
License
Proprietary API, interchange plus pricing
Maintained by
Adyen N.V.
Typically used for
Global card payments, local methods across many countries, in-person POS, payouts, enterprise risk management

The honest version

Adyen pros and cons

No technology is all upside. This is where Adyen earns its place and where it tends to cause trouble.

Where Adyen is strong

  • Single contract across many countriesInstead of integrating a different processor per region, you add payment methods per country from the same Adyen account, which is a material simplification at scale.
  • Own acquiring in most regionsAdyen holds its own licenses in the US, EU, UK, Singapore and more, which cuts out intermediate processors and typically improves approval rates.
  • In-person and online convergeThe same account, payment methods and risk engine cover e-commerce, POS terminals and mobile taps, which matters for omnichannel retail.
  • Strong risk and fraud toolsRevenue Protect lets you tune rules against real transaction data and catches more fraud than off-the-shelf rulesets without a wholesale reject rate jump.
  • Reliable payoutsSettlement is predictable, and payouts to marketplaces and multi-party flows work through Adyen for Platforms without a separate product bolted on.

Where Adyen bites

  • Enterprise onboarding is slowKYB, risk review and account structure can take weeks, with multiple back-and-forths that land outside engineering. This is not a self-serve experience.
  • Documentation is deep but denseEverything is documented, and the docs assume you already know the domain. Finding the right page for a specific 3DS scenario is its own skill.
  • Drop-in and components have sharp edgesThe web components work well when configured correctly, and fail silently when not. A missing payment method in the country configuration shows as an empty Drop-in with no error.
  • Webhooks require careful handlingHMAC signing, idempotency and retries are all your responsibility. Adyen will deliver a notification many times across days, and a broken handler has consequences.
  • Fees are negotiable but opaqueInterchange plus pricing is fair in principle and hard to compare to Stripe's headline rate, which makes the procurement conversation longer than expected.
  • Smaller community than StripeStack Overflow answers and third-party tutorials are fewer and often outdated. You rely more on the official docs and your account manager.

Sound familiar?

Common Adyen problems we fix

The Adyen problems that bring people to us, and what you have once each one is fixed.

Notification HMAC signature validation failed

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

3DS2: challengeShopper, fingerprint timeout

3DS2 flows keep falling back

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

Drop-in: payment method 'ideal' not configured

Drop-in shows an empty list

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

Recurring contract missing: shopperReference not stored

Recurring charges fail silently

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

AUTHORISATION refused: reason '3D Not Authenticated'

SCA declines are climbing in the EU

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

CHARGEBACK: liability shift not available

Chargebacks are hitting without a defense

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

Checkout API: X-API-Key invalid or revoked

API key rotations break production

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

Adyen help, from rescue to upkeep

Call us for one failing 3DS flow, or let us own the Adyen integration alongside your payments team.

Rescue
Refusals climbing, webhooks rejecting, or a Drop-in that shows an empty list to half your traffic. We stabilise first and explain second.
3DS2 and SCA
Authentication flows tuned per region, exemptions applied correctly, delegated authentication reviewed, and approval rates watched after each change.
Webhook reliability
HMAC verified, idempotency keyed on the right fields, retries safe to repeat, and a dead-letter path so a bad day does not swallow notifications.
Payment method configuration
Local methods enabled per country, Drop-in and Web Components wired to your checkout, and routing reviewed against approval rates per issuer.
Managed Tech
Ongoing watch on refusals, dispute response, risk rule reviews, API key rotations and a person to call when something inside the Customer Area shifts overnight.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Adyen alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Adyen questions

Something else? Call+1 737 727 7327

Why are our Adyen authorisation rates dropping?

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.

How do we handle Adyen webhooks reliably?

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.

Should we migrate from Stripe to Adyen?

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.

Why is our 3D Secure flow failing in Europe?

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.

Can we use Adyen for subscriptions?

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.

How much does Adyen help cost?

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

Adyen integration giving you trouble?

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.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.