How to retrieve a payment method on the client side?

Question

We are running an App with a Angular/Typescript frontend and a .NET backend, using Stripe Elements and Stripe.NET respectively.

We are currently using the "Sources" API.

The frontend can create sources, the backend saves them to our specific users. When you open the frontend again, the backend sends a list of source ids. The frontend then collects the data it needs to display those sources directly from Stripe so the user can pick one of his saved sources to pay and does not have to enter all the data again.

Enter the Payment Method / Payment Intend API.

Due to EU regulations Stripe has a new API that requires us to create cards no longer as "source" but as a "PaymentMethod". So I implemented that in the backend, opened the frontend in my IDE, updated the @types/stripe-v3 package and found the new payment intent API.

The only thing missing: I cannot figure out how the frontend is to access the payment method data, once created. I can create it. Send it to the backend. The backend can retrieve it. Send back the ID to the frontend... and now what? How to display the payment methods available?

I had expected a stripe.retrievePaymentMethod() as there is a stripe.retrieveSource(). But no such luck.

The only option I currently see to present the user with a list of existing payment methods is getting this info on the backend and piping it all, class by class, property by property to the client. Basically copying every single data class stripe has into our own backend REST definition. That cannot be right.

What am I missing? Why is there no stripe.retrievePaymentMethod() on the frontend? Did I not understand some fundamental facts about what those APIs should do?

Answer 1

After contacting Stripe directly, it was confirmed that that's just the way it is:

I think it's just an oversight that we didn't add one.

There are similar functions in the mobile SDK so I don't see why we shouldn't have it

There are no immediate plans to add the functionality back in in the very near future, so as a workaround, I will tunnel all the data through our backend(s).

Answer 2

If I understand as well, I think your problem is following and the sequence of that. I hope this helps you.