Guides · Free check · $9 fix pack

Guides

Stripe order stuck on "pending"? Handle delayed payments (ACH, bank debits)

"Donations stuck on Pending" and "the customer paid by bank and never got access" are the same bug. Some payment methods don't finish when Checkout finishes. If your webhook only listens for checkout.session.completed, the order waits for an event your app never receives.

Why it happens

Stripe: "Some payment methods aren't instant, such as ACH direct debit and other bank transfers. This means, funds won't be immediately available when Checkout completes. Delayed payment methods generate a checkout.session.async_payment_succeeded event when payment succeeds later" (Stripe docs: Fulfill orders). At the moment Checkout completes, the session's payment_status is unpaid, which Stripe defines as "The payment funds are not yet available in your account" (Stripe API: Checkout Session object).

The wait can be days, not seconds. Stripe lists ACH Direct Debit settlement timing as "Up to 4 business days" (Stripe docs: ACH Direct Debit). And "Payment methods with delayed notification can't guarantee the outcome while the payment is processing", so Stripe recommends "keeping the order pending and not fulfilling it until the payment succeeds" (Stripe docs: Immediate or delayed notification).

Two opposite bugs from the same gap

Stripe says automatic fulfillment with webhooks "is required if you sell subscriptions or accept payment methods with delayed success notification, because their subsequent state changes only after the Checkout Session completes" (source). A success-page unlock can't cover this case at all: the buyer has left long before the money arrives.

Check your endpoint's events

List your webhook endpoints with your live secret key and look at each one's enabled_events (Stripe API: List webhook endpoints). If it only lists checkout.session.completed, Stripe never sends the delayed result to it. Add checkout.session.async_payment_succeeded and checkout.session.async_payment_failed; both carry a Checkout Session object (Stripe API: Event types). If you only want card payments, you can instead limit the methods Checkout offers (the payment_method_types parameter on Create a Checkout Session, or your Dashboard's payment method settings).

The fix

  1. Keep one run-once fulfill(sessionId) function. It retrieves the session and returns early if payment_status is unpaid, as Stripe's guide does (source).
  2. Call it from both checkout.session.completed and checkout.session.async_payment_succeeded.
  3. On completed with unpaid, save the order as pending and tell the buyer the payment is processing, so they don't pay twice or open a support ticket.
  4. On async_payment_failed, mark the order failed, keep it locked, and ask the buyer to pay another way.
// Inside your verified Stripe webhook handler (after constructEvent succeeds)
switch (event.type) {
  case 'checkout.session.completed': {
    const s = event.data.object;
    if (s.payment_status === 'unpaid') {
      await db.orders.markPending(s.id);   // show "payment processing", don't unlock yet
    } else {
      await fulfillCheckout(s.id);         // run-once: retrieves the session, unlocks once
    }
    break;
  }
  case 'checkout.session.async_payment_succeeded':
    await fulfillCheckout(event.data.object.id); // the bank payment cleared: unlock now
    break;
  case 'checkout.session.async_payment_failed':
    await db.orders.markFailed(event.data.object.id); // keep locked, ask for another payment method
    break;
}
return new Response('ok', { status: 200 });

Rename the helpers to match your app. Events can arrive more than once and out of order, so fulfillCheckout must be safe to repeat and markPending must never re-lock an order that is already fulfilled (duplicate events).

Orders that are already stuck

List Checkout Sessions with status=complete for the last few weeks, and run your fulfill function for every one whose payment_status is now paid but whose order is still pending. The daily job in reconcile missed webhook events does exactly this and skips sessions that are still unpaid.

Bank debits can also be reversed after they succeed: "Customers can generally dispute an ACH Direct Debit payment through their bank for up to 60 calendar days after a debit on a personal account" (source). Revoke access on disputes too (refund or dispute doesn't revoke access).

Prompt for your AI builder

Fix Stripe fulfillment for delayed payment methods (ACH and other bank debits). 1) Keep one server-side fulfill function that takes a Checkout Session ID, retrieves the session from Stripe, returns early if payment_status is unpaid, and grants access only once per session (safe to call many times). 2) In the verified webhook handler, on checkout.session.completed: if payment_status is unpaid, save the order as pending and show "payment processing" to the user; otherwise call fulfill. 3) On checkout.session.async_payment_succeeded, call the same fulfill function. 4) On checkout.session.async_payment_failed, mark the order failed, keep access locked and show a "payment failed, try another method" message. 5) Never move a fulfilled order back to pending. 6) Tell me to add checkout.session.async_payment_succeeded and checkout.session.async_payment_failed to the webhook endpoint's events in the Stripe Dashboard. 7) Do not change the webhook signature check.

Re-test in a sandbox

  1. Turn on ACH Direct Debit for the sandbox and add both async events to your sandbox endpoint.
  2. Pay with Stripe's test bank account 000123456789, routing number 110000000 ("The payment succeeds"). Stripe notes you "need to verify all test accounts that automatically succeed or fail the payment", using test microdeposit amounts 32 and 45 (Stripe docs: Accept an ACH Direct Debit payment (Checkout)). The order should go pending, then unlock when async_payment_succeeded arrives.
  3. Repeat with 000222222227 ("The payment fails due to insufficient funds"). The order should end failed and stay locked.
  4. Card payments should still unlock straight away. To re-check without new payments, see test a webhook fix without a new payment.
Check yours in 10 seconds (free).

Paste your webhook URL. WebhookProof sends 3 harmless test requests and tells you whether Stripe can reach it and whether it rejects unsigned events. If it finds a problem, the $9 fix pack gives you the exact copy-paste fix for your stack (refundable for 14 days).

Run the free check

FAQ

Why is my Stripe Checkout order stuck on pending?

The buyer paid with a delayed method such as ACH Direct Debit. Checkout completes with payment_status unpaid, and the result arrives later as checkout.session.async_payment_succeeded or checkout.session.async_payment_failed. If your endpoint is not subscribed to those events, or your code ignores them, the order never moves.

Should I grant access on checkout.session.completed?

Only if the session's payment_status is not unpaid. Stripe's fulfillment guide checks payment_status and also fulfills on checkout.session.async_payment_succeeded for delayed payment methods.

How long can an ACH payment take?

Stripe lists ACH Direct Debit settlement timing as up to 4 business days, and a personal-account debit can generally be disputed for up to 60 calendar days.

Sources

More guides

Stripe webhook not working? Check these 7 things in order · A customer paid but didn't get access. What went wrong? · No signatures found matching the expected signature for payload · Stripe webhook failing with a 307 or 308 redirect

Last reviewed 2026-11-05. WebhookProof is an independent tool, not affiliated with Stripe, Inc.. Quotes are from the linked documentation.