---
description: Learn what the Stripe requires_payment_method status means, why it happens on PaymentIntents, and how to resolve it by attaching a new payment method.
title: Stripe requires_payment_method Status Explained
image: https://cdn.smartretry.com/_next/static/media/og-image.0z0q4_5kazzzo.jpeg
---

[Skip to main content](#main-content)

Stripe · Status

# Stripe Status requires\_payment\_method: Requires Payment Method

The PaymentIntent has been created but no payment method has been attached yet, or the previous payment attempt failed and a new payment method is needed. The merchant/developer must collect and attach a payment method before proceeding.

## What it means

The requires\_payment\_method status is a Stripe-specific processing state on a PaymentIntent or SetupIntent. It indicates that the transaction cannot proceed because a valid payment method has not been provided. This occurs either immediately after the intent is created, or when a previous payment attempt fails (such as an issuer decline or an SCA failure) and Stripe clears the association. The intent waits in this state until a new or updated payment method is successfully attached.

## Classification & retryability

softtechnicalRetryable: conditional

Do not automatically retry the same failed payment method. You must collect a new payment method or perform on-session SCA authentication, attach it to the existing PaymentIntent, and call the confirm endpoint again.

## Common causes

* A PaymentIntent or SetupIntent was just created without an attached payment method.
* The previously attached payment method failed authorization, such as an issuer card decline.
* An off-session payment failed because Strong Customer Authentication (SCA) was required by the issuer.
* The customer abandoned the checkout flow before submitting their card details.

## How to resolve it

To resolve this status, the application must collect a new or updated payment method from the customer. Once the new payment details are obtained, attach them to the existing PaymentIntent or SetupIntent and call the API's confirm endpoint to re-attempt the transaction. If the transaction previously failed due to off-session SCA requirements, bring the customer on-session to re-authenticate.

### For merchants

Monitor your webhook events for payment\_intent.requires\_payment\_method. Check the last\_payment\_error property on the intent to determine why the previous attempt failed. Surface a clear error message to the customer, prompt them to provide an alternative payment method, and re-confirm the intent.

### For customers

Provide a valid, up-to-date payment method (such as a different credit card or a digital wallet) when prompted by the checkout interface. Complete any necessary 3D Secure authentication steps if requested.

## Sources

* [Stripe Docs – PaymentIntents lifecycle](https://docs.stripe.com/payments/paymentintents/lifecycle)
* [Stripe Docs – Payment status updates](https://docs.stripe.com/payments/payment-intents/verifying-status)
* [Stripe API Reference – PaymentIntent object](https://docs.stripe.com/api/payment%5Fintents/object)
* [Stripe Support – Manual confirmation for off-session payments requiring SCA](https://support.stripe.com/questions/manual-confirmation-for-off-session-payments-requiring-strong-customer-authentication-%28sca%29)

---

```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.smartretry.com/"},{"@type":"ListItem","position":2,"name":"Decline Code","item":"https://www.smartretry.com/decline-code"},{"@type":"ListItem","position":3,"name":"Stripe","item":"https://www.smartretry.com/payment-providers/stripe"},{"@type":"ListItem","position":4,"name":"requires_payment_method","item":"https://www.smartretry.com/decline-code/stripe-status-requires-payment-method"}]}
```