Is Affirm Down? How to Tell and What to Do

Affirm is a buy-now-pay-later (BNPL) payment provider deeply integrated into e-commerce checkouts across major retailers and direct-to-consumer brands. When Affirm goes down, customers who try to select it as a payment method hit errors or see the option disappear entirely — and many won't switch to an alternative. They'll leave. For merchants, an Affirm outage silently drains conversion rate until someone notices the revenue gap.

Statusfield brings reported Affirm incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.

Follow Affirm incidents with your team

Statusfield brings reported status for Affirm together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

Common Signs of an Affirm Outage

Symptom	What's likely happening
Affirm button missing or not rendering at checkout	Widget script failed to load from Affirm's CDN
"Affirm is temporarily unavailable" error message	Affirm's checkout API is returning errors
Affirm modal opens but spins and never loads	Session initialization request is timing out
Application approved but order not created	Order capture endpoint is failing
Affirm loan confirmed but merchant not notified	Webhook delivery from Affirm is degraded
Refund submitted but not reflected in Affirm dashboard	Refund/void API is down
Affirm Merchant Dashboard inaccessible	Merchant portal API is degraded

How to Confirm It's Affirm, Not You

Before pulling in your dev team for a code investigation, rule out issues on your side:

1. Check browser console for Affirm network errors Open Chrome DevTools (F12 → Network tab), attempt to load the checkout page with Affirm, and look for requests to cdn.affirm.com or api.affirm.com. Failed requests with 502, 503 or timeout responses give you evidence to investigate. Compare timestamps and request IDs with vendor reports; these responses alone do not establish the cause.

2. Test with a different payment method Complete a test order using a credit card or another payment method. If other methods work, focus your investigation on the Affirm integration, including its credentials, configuration and vendor reports.

3. Check your Affirm Merchant Dashboard Log into the Affirm Merchant Portal and verify it loads and shows recent transaction data. If the portal also fails, check vendor reports and try another network to narrow the scope.

4. Test on a second browser or in incognito mode Cached Affirm widget scripts or stale authentication tokens can sometimes cause checkout failures that look like outages. Open a fresh incognito window and run through the full checkout flow from scratch.

5. Watch your payment step drop-off rate If you have real-time analytics, look for an unusual spike in abandonment specifically at the payment step. A sudden jump in payment-step exits that coincides with when Affirm started failing is a clear signal — even before you've confirmed the root cause.

Use vendor reports as investigation context

A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.

What to Do During an Affirm Outage

Immediate (first 5 minutes)

Review reported vendor incidents alongside your own request logs. A matching incident adds context but does not establish the cause of your failure.
Check whether your checkout can surface a conditional message when Affirm fails to initialize, such as "Affirm is temporarily unavailable — please use another payment method." Many Shopify, WooCommerce, and custom integrations support error state messaging for Affirm.
Check your live order rate and payment-step conversion to quantify the impact.
Alert your customer support team immediately so they can answer inbound questions accurately instead of asking customers to repeatedly retry.

Communication (first 15 minutes)

If you're mid-promotion or in a high-traffic period, consider a brief site notice or social post: "We're aware Affirm is experiencing issues. Other payment methods are available and working normally."
Brief your support team with consistent talking points: the issue is on Affirm's side, other payment methods work, and Affirm is expected to resolve it. Avoid speculating on timelines.
If you have an Affirm merchant success contact, notify them — enterprise accounts sometimes receive proactive communication that doesn't appear on the public status page.

Recovery

Once Affirm restores service, confirm that any orders stuck in intermediate states (approved but not captured) have resolved correctly.
Review webhook delivery logs for the outage window and ensure all fulfillment-triggering events arrived at your system.
Check refund requests initiated during the outage to confirm they processed completely.
Pull cart abandonment data for the outage window and evaluate whether a recovery email to those customers is appropriate.

Affirm Components and What Each Outage Looks Like

Component	Impact when degraded
Affirm CDN (Widget Script)	Affirm button doesn't render; payment option invisible to customers
Checkout API	Modal opens but fails; customers can't apply or complete Affirm payment
Loan Authorization	Application completes but loan not approved; order not created
Order Capture	Loan authorized but merchant doesn't receive confirmation; fulfillment blocked
Webhook Delivery	Order events not sent to merchant systems; OMS/ERP not updated
Refund API	Refunds submitted but not processed; customer disputes may escalate
Merchant Dashboard	Portal inaccessible; merchant can't review loans, disputes, or payouts

Match the check to the failure you need to catch

Follow supported Affirm components for vendor-reported incidents. Add a public HTTPS check for your own website or API and define acceptable response codes, response time and body checks. A successful request is evidence about that endpoint, not proof that an entire customer journey works.

Use application logs and end-to-end tests for authenticated workflows, data correctness and transactions. Statusfield brings the monitoring results and vendor context together; it does not run a complete checkout or login flow.

Bring Affirm updates to your team

Follow reported Affirm status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.

Eligible first-time customers can start a free trial, no credit card required.

Follow Affirm incidents with your team

Follow Affirm and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

FAQ

Is Affirm down right now?

This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.

How can I get alerts about Affirm incidents?

Does an operational Affirm status mean my application is working?

No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.

Browse the service catalog and plans and alert destinations.

Is Affirm Down? How to Tell and What to Do