#beadle
safe tinsel
frosty current
Hey @median dagger , thanks for hopping on to help!
median dagger
Hi, can you share the request id where you're seeing this error? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
frosty current
req_IEgoZyeYYd8Upl
median dagger
Thank you. The reason why you see this error is because that invoice already has a Payment Intent Created: https://dashboard.stripe.com/events/evt_3Ms43OCyKWiVyev00Hlnru02 for that invoice. You cannot update this, instead, you'd need to create a new invoice with the updated allowed Payment Methods.
frosty current
Hmm, let me check something real quick.
Ok, I just updated the payment methods on an invoice that already had a payment intent. So, the fact that an invoice already has a payment intent created does not keep you from updating.
median dagger
Can you share that request id with please?
frosty current
req_GILpSjDdDyYr2i
median dagger
I was able to further look, you're right. From looking at the error code on my end, you cannot update the Payment Method type when the attached payment method doesn't match the type you're trying to update to.
frosty current
Yes, that is my understanding as well. The weird thing is that the payment intent for the invoice I am trying to update should never have had "card" as an option. The invoice was created from a subscription set to "email invoice to customer" and the only allowed payment method was set to "ach_credit_transfer".
For example, why does the following payment intent have credit card as an option for payment?
pi_3Ms6pzCyKWiVyev00QkmDdit
median dagger
Looking
frosty current
Here you can see the invoice and the associated payment intent. The invoice only allows for ACH credit transfer but the payment intent grabbed the customers credit card. 🤷🏻♂️
median dagger
So these are separate. The setting for ACH credit Transfer is only for that invoice. The customer's default source, sits on the customer object and not on the invoice object. Here, you attached a default source, https://dashboard.stripe.com/logs/req_xfrbc59wutFW6R as the payment method.
frosty current
Ok, so that added a default source to the customer object correct?
median dagger
That is correct.
frosty current
The invoice we sent the customer didn't allow for card payment.
It only allows for ACH Credit Transfer.
So, why does the payment intent for this invoice have their card attached as a source when card payment isn't an option for this invoice?
Because the payment intent has an unusable source attached to it, it won't allow me to modify the payment methods for the associated invoice. Sorry, it just doesn't make sense to me.
median dagger
Yeah, I do not disagree with you here. Let me double check with a teammate.
frosty current
Thanks!
median dagger
I was able to confirm here that it's expected. We always let the "default source" or "default payment method" allowed on top of those settings for the allowed payments on the invoice. It's easy for people to get those settings out of date and so if you don't want card at all, you should set it on the Subscription: https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_settings-payment_method_types
frosty current
Yup, the subscription is (and was) set to not allow credit card. 😅
We gathered the customers credit card information separately through out app to use with in-app purchases. However, they're subscription doesn't allow for credit cards.
sub_1MkUzMCyKWiVyev0vsvMuw0q
median dagger
I do not see this on your Subscription creation request: https://dashboard.stripe.com/logs/req_Ppwitrjm7O8d76
That looks like a different Subscription id.
frosty current
Sorry, I have a few different ones that all have the same issue.
Couldn't remember which customer we were originally working with.
median dagger
Let's work with the same customer, https://dashboard.stripe.com/logs/req_Ppwitrjm7O8d76
frosty current
Copy that.
Does it not default to ACH Credit Transfer for a subscription if payment method types aren't specified?
median dagger
No, you'd need to specifically pass the payment method types on creation.
frosty current
Ahh, ok. That must have been where we went wrong. We were relying on the Invoice Template settings to enforce what payment methods would be used for all the subscriptions in which we were planning on using "send invoice" as opposed to "charge default payment method".
Thanks for all your help today! I'm definitely have a better grasp on Stripe and how it works. Hope you have a good rest of your shift.
median dagger
Thank you!