Payments for existing customers

Call the list Payment Method endpoint with the allow_redisplay parameter to retrieve a customer’s reusable payment methods.

curl -G https://api.stripe.com/v1/customers/{{CUSTOMER_ID}}/payment_methods \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -d allow_redisplay=always

Use the API response data to display the Payment Methods in your own UI and let the customer select one.

Create a PaymentIntent to try to charge the customer with the payment method they selected.

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -d amount=1099 \
  -d currency=usd \
  -d customer={{CUSTOMER_ID}} \
  -d payment_method={{PAYMENT_METHOD_ID}} \
  -d confirm=true \
  --data-urlencode return_url="https://example.com/order/123/complete"

If the API call fails with a 402 response, it means the payment was declined. Ask the customer to try again or use a different payment method.

Assuming the PaymentIntent is successfully created, check its status:

• succeeded indicates the customer was charged as expected. Display a success message to your customer.
• requires_action indicates you must prompt additional action, such as authenticating with 3D Secure. Call handleNextAction on the frontend to trigger the action the customer needs to perform.

const { error, paymentIntent } = await stripe.handleNextAction({
  clientSecret: "{{CLIENT_SECRET}}"
});

if (error) {
  // Show error from Stripe.js
} else {
  // Actions handled, show success message
}

Stripe sends a payment_intent.succeeded event when the payment completes. Use the Dashboard webhook tool or follow the webhook guide to receive these events and run actions, such as sending an order confirmation email to your customer, logging the sale in a database, or starting a shipping workflow.

Listen for these events rather than waiting on a callback from the client. On the client, the customer could close the browser window or quit the app before the callback executes, and malicious clients could manipulate the response. Setting up your integration to listen for asynchronous events is what enables you to accept different types of payment methods with a single integration.

In addition to handling the payment_intent.succeeded event, we recommend handling these other events when collecting payments with the Payment Element: