overture8-payment-methods

[queen wind]

Hi 👋 these are different types of objects that can be used as payment methods. Payment methods (pm_XXX) are our newest objects that were preceded by cards and sources.
https://stripe.com/docs/payments/payment-methods/transitioning

[pulsar kraken]

Hi Toby. Thanks for this. I knew that src and card were old legacy stuff. I was just surprised that they were still being used. When looking at the logs (in Stripe) at "src" ones, they were created via invoice.stripe.com - which I think is just a customer updating a failed payment. Anything that was "card" was showing in the Stripe event logs as created via the Stripe dashboard. All the "pm" ones were created by us directly via the API.

Is that the way it works?

[queen wind]

Do you have an ID from one of these source or card objects that was created recently?

[pulsar kraken]

Here is one that was created today. src_1K17h0ARBCSE74STGLIEGT2K

[tiny hare]

@pulsar kraken looking give me a sec

@pulsar kraken correct, Sources are still created by Hosted Invoice Pages and Dashboard still creates Card objects

All are forward compatible with PaymentMethods, meaning on your end, if you fetch a Customer's PaymentMethods, you'll get back their attached PaymentMethod, then Sources and Cards as well

anywhere where you can pass a payment_method parameter, you can also pass a Source ID or Card ID in place of a PaymentMethod ID

[pulsar kraken]

Ah, great! one further question. Are "src" and "card" payment methods created in that way reusable? (like setup intent payment methods).

[tiny hare]

so half-yes

yes, that they are re-usable like PaymentMethods are, if attached to a customer

(like setup intent payment methods).
if they are run through a SetupIntent, then yes they would be "set up" for SCA exemptions too