windlepoons-customer | Stripe Developers | Page 1

haughty crystal Oct 6, 2021, 6:02 PM

#

@gentle imp what are you really trying to do? Source objects are deprecated in most cases and no one should be using them in most cases. What are you really trying to answer

gentle imp Oct 6, 2021, 6:04 PM

#

We have legacy customers that have them still. AFAIK there is no automated way to move them to payment methods. I'm replacing calls to Stripe to use our cache, some of them expand sources for legacy users. If they have a payment method, I can avoid loading sources, but if they have sources, it'd be nice to fetch just the sources to add them back instead of fetching the customer record again.

#

(add them back == fetch just them and merge them into the customer object we fetched from cache)

haughty crystal Oct 6, 2021, 6:14 PM

#

what kind of type of Source? There are many. Is this only cards?

gentle imp Oct 6, 2021, 6:14 PM

#

Whatever is typically on customer.sources?

#

We've only stored credit cards, yes.

haughty crystal Oct 6, 2021, 6:16 PM

#

Okay it's important because there are 20+ types of Source objects (card, sepa_debit, ach_credit_transfer, etc.)

#

All card Sources src_123 100% work as PaymentMethods via the API already. If you use https://stripe.com/docs/api/payment_methods/list for that Customer you would see all the src_123 and you should never use the old approach

gentle imp Oct 6, 2021, 6:17 PM

#

Ah, so payment methods will list all sources?

#

Okey, thanks!

#

If there's a default_source, that id can be found in payment methods?

haughty crystal Oct 6, 2021, 6:19 PM

#

yes

#windlepoons-customer