Why are Adyen payments failing but the status page shows operational?

Status pages reflect global averages — regional degradation, issuer-side failures, or account-specific issues may not trigger a status update. If Adyen payments are failing, check status.adyen.com for your region, verify your API credentials are valid, confirm the shopper's issuing bank is not declining (error code REFUSED vs TECHNICAL_ERROR indicates issuer vs Adyen), and check your webhook logs for error codes.

What does Adyen error code TECHNICAL_ERROR mean?

TECHNICAL_ERROR from Adyen typically means a connection or processing issue on Adyen's side, distinct from REFUSED (issuer declined) or INVALID_CARD_NUMBER (validation error). During an Adyen outage, TECHNICAL_ERROR rates spike. Track this error code in your payment analytics — a sudden spike is a leading indicator of Adyen issues even before the status page updates.

Does Adyen have separate status per region?

Yes. Adyen operates across multiple regions including EU (live.adyen.com), US (live.adyen.com/v1/us-...), AU, Asia-Pacific, and others. An incident in the EU processing environment may not affect the US environment. status.adyen.com shows per-region and per-service status. Always confirm which live endpoint your integration uses — the region is embedded in your live API prefix.

How do I get alerts when Adyen goes down?

Subscribe to status updates at status.adyen.com (email/RSS), monitor your payment success rate and TECHNICAL_ERROR volume in real time, and use an independent uptime monitor on your Adyen checkout endpoint. Set alerts for payment success rate dropping below your baseline — this catches Adyen degradation faster than waiting for an official status page update.

Adyen / Payments & Fintech

Adyen Status: How to Check If Adyen Is Down Right Now (2026)

Updated June 2026 · 8 min read · API Status Check

Quick Answer

Check Adyen status at status.adyen.com (official) for real-time payment processing status across all Adyen regions and services.

Staff Pick

📡 Monitor your APIs — know when they go down before your users do

Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.

Start Free →

Affiliate link — we may earn a commission at no extra cost to you

The Official Adyen Status Page

Adyen maintains an official status page at status.adyen.com. This page tracks real-time status across all Adyen payment services and regions:

Payment Processing: The core card authorization and capture pipeline — what merchants care about most. Covers all payment methods: cards, wallets, local payment methods

Checkout API: The Adyen Checkout API used by web and mobile integrations to initiate payment sessions and process transactions

Terminal API (In-Store): API for point-of-sale terminal integrations — critical for physical retail. A Terminal API outage means in-store card payments fail

Merchant Portal: The Customer Area (ca.adyen.com) for transaction reporting, refunds, and configuration — management plane separate from payment processing

Webhook Delivery: Notification webhooks that confirm payment outcomes (AUTHORISATION, CAPTURE, REFUND notifications) — failures here cause reconciliation issues even if payments succeed

Payout Processing: Settlement and payout disbursement to merchant bank accounts — typically processed on a schedule, failures affect merchant cash flow

What Each Adyen Status Means

Operational: All Adyen payment processing working normally. Payment success rates are within expected range. If payments are still failing, the issue is likely the shopper's issuing bank (REFUSED result code) or a configuration/credential issue on your side.

Degraded Performance: Adyen is processing payments but with elevated latency or higher-than-normal TECHNICAL_ERROR rates. Payment success rates may be below baseline. Monitor your checkout conversion rate closely — even degraded performance noticeably impacts revenue.

Partial Outage: A specific Adyen service or region is affected. Often a single payment method (e.g., SEPA Direct Debit) or a specific acquiring region fails while card processing in other regions continues. Check which services are affected and whether your payment mix includes the impacted method.

Major Outage: Adyen payment processing is broadly unavailable. All payment attempts return TECHNICAL_ERROR. For merchants with high transaction volume, even a 5-minute major outage represents significant lost revenue. Have your runbook ready for communicating with customers.

Under Maintenance: Planned maintenance window. Adyen typically performs maintenance on non-peak hours and announces windows in advance via status.adyen.com. Payment processing usually continues during maintenance, but management plane (Customer Area) may be affected.

📡

Recommended

Monitor your payment success rate independently

Better Stack monitors your Adyen checkout endpoints and payment webhooks — so you catch degradation in payment processing before it shows up on Adyen's status page. Free tier included.

Try Better Stack Free →

Adyen Regional Environments: Which One Are You Using?

Adyen routes payments through regional live environments. Understanding which environment your integration uses is critical during outages — an EU incident may not affect your US transactions:

EU Live Environment

The primary Adyen environment for European merchants. API endpoint prefix: live.adyen.com/v1/[randomprefix]-live (EU region). The most widely used environment for European card schemes (Mastercard, Visa Europe, local payment methods like iDEAL, SEPA).

US Live Environment

US acquiring environment with endpoint suffix -live-us-. Critical for merchants processing US card-present and card-not-present transactions. Separate acquiring infrastructure from EU — US incidents are typically isolated.

AU / Asia-Pacific Environment

Australian and APAC merchants use a distinct live environment (-live-au- suffix). Also covers Singapore and other APAC markets. Local payment methods like PayID and Alipay route through this environment.

Test Environment

checkout-test.adyen.com / test.adyen.com — used for integration testing and staging. If test is down but live is operational (or vice versa), production impact depends on which environment your issue affects. Test outages should not affect production payments.

5 Ways to Check Adyen Status Right Now

Official Adyen Status Page

Visit status.adyen.com for real-time status across all Adyen services and live environments. Subscribe to email or RSS for incident notifications.

status.adyen.com →

Monitor Your Payment Success Rate

Your own payment success rate is the most reliable leading indicator. A sudden spike in TECHNICAL_ERROR result codes signals Adyen issues before the official status page updates. Set up dashboards in your analytics or payment management system.

X/Twitter Search

Search 'Adyen down' or 'adyen outage' on X. Since Adyen powers payments for large retailers (Nike, Spotify, McDonald's, Microsoft), social reports appear quickly during outages.

Search X for 'adyen down' →

Adyen Customer Area Logs

Log into ca.adyen.com → Transactions → Payments to check recent transaction results in real time. A surge in TECHNICAL_ERROR results confirms Adyen-side issues vs. REFUSED (issuer) or validation errors.

Adyen Customer Area →

Test Your Live Endpoint Directly

Send a test payment with a known card number to your live environment to confirm whether the issue is widespread or account-specific.

# Check Adyen Checkout API latency
curl -o /dev/null -s -w "HTTP %{http_code} — %{time_total}s\n" \
  -X POST https://checkout-live.adyen.com/v71/sessions \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY"

# A 401 means credentials issue, 5xx means Adyen-side failure

Common Adyen Errors During Outages

These are the errors and result codes you'll see when Adyen is experiencing issues:

"resultCode: TECHNICAL_ERROR"Adyen-side processing failure — not an issuer decline. Spikes in TECHNICAL_ERROR indicate Adyen infrastructure issues. If you see this rate jump above your baseline, check status.adyen.com immediately. This is the key metric to monitor for Adyen health.

"HTTP 500 from checkout-live.adyen.com"The Adyen Checkout API is returning internal server errors. Payment sessions cannot be created and existing sessions may fail to authorize. This is a clear signal of Adyen-side issues, not client-side.

"HTTP 504 Gateway Timeout on Adyen API"Adyen API is accepting connections but timing out before responding. Common during degraded performance incidents. Implement retry logic with exponential backoff — but be careful of double-charging if retrying authorization calls.

"Webhook notifications not arriving"Adyen webhook delivery is delayed or failing. Payments may have succeeded but your system hasn't received AUTHORISATION notifications. Check Adyen Customer Area for actual payment results and implement webhook replay/retry handling.

"resultCode: ERROR (not TECHNICAL_ERROR)"Generic error, often configuration-related. Check your merchant account settings, API credentials, and that the payment method is enabled for your merchant account. Less likely to be an Adyen outage — more likely a misconfiguration.

"Terminal offline / Cloud API timeout"Adyen Terminal API is unreachable. In-store POS devices show offline or card-present payments fail at the terminal. Check status.adyen.com for Terminal API status specifically — this is tracked separately from online Checkout API.

What to Do When Adyen Is Down

Immediate Response

Confirm at status.adyen.com — check your specific live environment
Check TECHNICAL_ERROR rate in Adyen Customer Area → Transactions
Display a clear checkout error to customers — avoid generic "try again" if Adyen is confirmed down
If you have a PayPal or Stripe fallback, activate it immediately
Alert your support team — expect increased customer contacts
Document the incident start time for post-mortem and potential SLA credit claim

Long-Term Resilience

Implement a secondary payment processor (Stripe, Braintree) as failover
Build payment success rate alerting — threshold below your baseline triggers PagerDuty
Store payment intents locally so you can replay when Adyen recovers
Implement idempotency keys on all Adyen API calls to prevent double-charges on retry
Test your fallback payment flow regularly — not just during incidents

Who Uses Adyen?

Adyen is the payments backbone for some of the world's largest brands. Understanding who uses Adyen helps calibrate the business impact when it goes down:

Retail & E-Commerce: Nike, IKEA, Decathlon, H&M, Crocs — major retailers processing billions in card-not-present and in-store payments globally

Tech & Digital: Spotify, Uber, Airbnb, Booking.com, eBay — high-volume subscription and marketplace payments where milliseconds matter

Food & QSR: McDonald's, Subway, Domino's — high-frequency point-of-sale Terminal API integrations where Terminal API availability is critical

Enterprise SaaS: Microsoft, Salesforce — B2B payment processing at enterprise scale, often with complex acquiring arrangements across regions

Frequently Asked Questions

Where is the official Adyen status page?

Adyen's official status page is at status.adyen.com. It shows real-time status for payment processing, Checkout API, Terminal API, webhook delivery, and the merchant portal (Customer Area). You can subscribe to incident notifications via email or RSS. The page is hosted on Atlassian Statuspage.

Is Adyen down for everyone or just me?

Check status.adyen.com first — if it shows operational but your payments are failing, the issue may be isolated to your account, your live environment, or a specific payment method. Check Adyen Customer Area transaction logs for error patterns. TECHNICAL_ERROR spikes = Adyen-side issue. REFUSED spikes = issuer-side issue. Validation errors = configuration issue.

How do I know if Adyen is causing my payment failures vs. the bank?

Adyen result codes are specific: REFUSED = issuer (bank) declined the transaction. TECHNICAL_ERROR = Adyen processing failure. ERROR = configuration or credential issue. During an Adyen outage, you'll see TECHNICAL_ERROR rates spike sharply across all card types and regions. REFUSED rates fluctuating normally while TECHNICAL_ERROR spikes almost always means Adyen-side issues.

Does Adyen have an SLA I can claim credits from?

Adyen offers SLAs under enterprise agreements that typically include monthly uptime commitments. During confirmed incidents, you can request SLA credit through your Adyen account team. Document the incident start/end time from status.adyen.com and your own transaction logs to support a credit request.

What's the difference between Adyen and Stripe for reliability?

Both Adyen and Stripe are enterprise-grade payment processors with strong uptime records. Adyen operates its own global acquiring licenses and payment infrastructure end-to-end (it is both the gateway and acquirer in most markets), which gives it different failure modes than Stripe. For maximum reliability, large merchants implement both as primary and failover processors.

Alert Pro

14-day free trial

Stop checking — get alerted instantly

Next time Adyen goes down, you'll know in under 60 seconds — not when your users start complaining.

Email alerts for Adyen + 9 more APIs
$0 due today for trial
Cancel anytime — $9/mo after trial

Start Free Trial →Compare all plans →

Also recommended:

Better Stack — all-in-one monitoring 1Password — secure your API keys