Stripe "status": "requires_payment_method",

Stripe "status": "requires_payment_method",

  1. Blog
  2. 15 November 2026
  3. 4 min read

Stefan Bogdanescu

Founder & Senior Architect

Stripe "status": "requires_payment_method"

When integrating Stripe payments, encountering a status of requires_payment_method is a specific signal that your payment intent has not yet been collected from the user. This error typically appears when you attempt to process a payment using legacy tokenization methods on a Payment Intent architecture that requires direct client-side element collection and confirmation.

The root cause in your scenario stems from a mismatch between how Stripe's modern Payment Intents work and how the JavaScript is being initialized. In the provided code, you are creating a card element and mounting it to #card-element. However, the core logic inside the form submit handler relies on stripe.createToken(card).

This is the critical failure point. The createToken method was part of the older Elements v1 or early v2 era, designed for legacy Checkout flows or direct charges. It does not interact with a Payment Intent ID (intent_id) that you have already created and stored in your database. When Stripe receives a request to create a token without an associated intent context, it flags the payment as incomplete because it doesn't know which charge to associate the new card data with.

To resolve this, you must shift from createToken to confirmCardPayment. This method tells Stripe: "Here is the Payment Intent ID I created on the server; here is the Card Element data from the browser; please finalize the payment."

You need to update your JavaScript initialization and submission logic as follows. First, ensure the Stripe.js library is loaded before the script executes. Then, pass the intent_id to the confirmation function.

const stripe = Stripe('pk_test_...'); // Replace with your publishable key

// Initialize elements
const elements = stripe.elements();
const style = { base: { fontSize: '16px', color: '#32325d' } };
const cardElement = elements.create('card', { style });
cardElement.mount('#card-element');

// Reference the hidden input containing the client secret from your server
// This should be populated by PHP/Laravel as shown in your source code
const stripeCardElement = cardElement; 

const form = document.getElementById('payment-form');

form.addEventListener('submit', async (event) => {
  event.preventDefault();

  // Use confirmCardPayment instead of createToken
  const { error, paymentIntent } = await stripe.confirmCardPayment(
    'pi_xxx_yyy_zzz', // Replace with the actual intent_id from your hidden input
    { 
      payment_method: {
        card: cardElement,
        billing_details: { 
          name: document.getElementById('cardholder-name').value 
        }
      }
    }
  );

  if (error) {
    // Display error message
    const displayError = document.getElementById('card-errors');
    displayError.textContent = error.message;
  } else {
    // Success: The paymentIntent object contains the transaction result
    console.log('PaymentIntent:', paymentIntent);
    
    // If you are using Stripe Elements v3, confirmCardPayment returns the status.
    // You can redirect to a success page here if needed.
  }
});

Handling Hidden Inputs and Client Secrets

In your PHP/Laravel code snippet, you correctly output the client_secret into a hidden input field:

<div id="intent_id" value="<?php echo HTML::output($stripe_payment_intent_id); ?>">
<div id="secret" value="<?php echo HTML::output($this->intent->client_secret); ?>">

However, when using confirmCardPayment, the client_secret is technically not required to be passed as a separate argument in the latest Stripe Elements v3 library because the library automatically retrieves the necessary state from the mounted Card Element. But if you are using a specific version of the library or a custom backend handler that expects the secret, ensure the hidden input is named correctly (often stripe_client_secret) and matches what your backend API endpoint expects.

Backend Confirmation

If your PHP script handles the confirmation request after the JS submission, ensure the backend call uses the correct payload. You cannot send a token ID to your server if you are using Payment Intents with client-side confirmation. Your server endpoint must accept the client_secret (if required by your setup) or simply the result of the successful confirmCardPayment response and process the webhook for idempotency.

Legacy vs. Modern Patterns

The confusion often arises because older Stripe documentation tutorials use createToken. If you are strictly following a tutorial that uses createToken, that tutorial is likely outdated for new Payment Intent implementations. The modern standard involves:

  1. Creating an intent on the server (POST /v1/payment_intents).
  2. Mounting the Card Element to a DOM element.
  3. Calling stripe.confirmCardPayment in the browser.

By switching your JavaScript from createToken to confirmCardPayment and ensuring the intent ID is passed correctly, the status will resolve from requires_payment_method to succeeded. For further details on accepting payments with Payment Intents, refer to the official Stripe documentation: https://stripe.com/docs/payments/accept-a-payment-charges#web.

Our network