#sabrina_41117

1 messages · Page 1 of 1 (latest)

harsh oasisBOT
vague pecan
#

We are using Sigma to view the payment_methods table.

woeful charm
#

👋 happy to help

#

would you mind sharing an example?

vague pecan
#

pm_1O4YP8Jaf89hC41IPYLyeLsD

woeful charm
#

theoretically speaking it is possible to add a payment method and not attach it to a customer

#

you're still using a super old API version

#

is that intentional?

vague pecan
#

No. What version are you seeing?

woeful charm
#

2014-12-22

#

this is the default version for your Stripe Account

vague pecan
#

What is the newest version?

woeful charm
#

but this is not related to your issue

#

what you're doing here is that you're creating a PaymentIntent for a customer but you're not setting setup_future_usage which means that the PM that is being created to pay that PI is not being attached to the customer

vague pecan
#

Ok. so how are some PMs attached to customers and some are not.

#

And what table is setup_future_usage set?

woeful charm
#

I'm not a Sigma expert, but normally setup_future_usage is set on the PaymentIntent

#

yes I just checked

vague pecan
#

I found setup_future_usage in the payment_intents table. 🙂

woeful charm
#

exactly

vague pecan
#

How are some PMs attached to customers and some are not?

woeful charm
#

depending on how you create them

#

if you use SetupIntents or PaymentIntents with setup_future_usage

#

or even if you manually attach a Payment Method to a customer

vague pecan
#

Weird. We are not seeing an common denominator between the payment methods that are missing Stripe customer IDs.

#

Seems to be a mix of card types, link, apple pay, etc...