Using Stripe to authorize and save a payment method to database for future use

michaelvictor · 2024-11-02T02:03:37.893Z

Hi world,

I’m hoping you can help me figure this out. In the My Account section of my app, I give users the option to save a payment card for future one-time or recurring purposes. Using Stripe Elements and Setup Intents, my goal is to:

Authorize and Validate the Card: I want to ensure the card is valid, not expired or stolen, and suitable for future use. Stripe Elements performs a basic check, but I’m trying to use Stripe’s Setup Intent action to do a more thorough verification.
Tokenize and Save the Card: After validating, I’d like to tokenize the card via Stripe, then save the tokenized information in my database for future use.

I can successfully create and save the payment method with Stripe, but integrating the validation step using Setup Intents is where I’m stuck.

The Problem: I’m having trouble interpreting Stripe’s response to determine whether a card is fully validated and ready to be saved. For example, when I test using Stripe’s known-bad test card numbers (like for insufficient funds or stolen cards), I’m not able to distinguish between a successful validation and a failed one. This makes it difficult to prevent invalid cards from being saved to the database.

Any insight or guidance on handling the Setup Intent response to differentiate valid from invalid cards would be greatly appreciated!

Screenshot 2024-11-01 at 10.00.30 PM1272×1132 70.2 KB

’m

michaelvictor · 2024-11-02T22:04:16.248Z

Just resurfacing this! Any thoughts?

Dimo · 2025-04-01T15:08:54.231Z

@michaelvictor

Hello,

have you found any solutions?