#guccisofloppy
1 messages · Page 1 of 1 (latest)
You can create a $0 authorization on their card: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
If this doesn't decline, then the card is active
I've hit an edge case where a user who has canceled their subscription is struggling to re-sign up. Each attempt at creating a new subscription returns the error: This customer has no attached payment source or default payment method. Please consider adding a default payment method, but in both the Dashboard and the CLI tool, I see PaymentMethods attatched to the customer
Do you have a Customer ID for the relevant customer and a Request ID for the API request that gave you that error code?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Thanks! Digging now
thanks. I'm a little in-over my head having taken over from another dev, so the order-of-events might be off
you guys are awesome, BTW, this is the best support I've encountered
you would need to set either the invoice settings of the Customer (https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method), or the default_payment_method of a particular subscription (https://stripe.com/docs/api/subscriptions/update#update_subscription-default_payment_method).
Since the Customer has 2 payment methods, there's no way for Stripe to know which one to choose, so it errors out
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
ahhhhhh, interesting! So if a user goes through the checkout process and attatches a PaymentIntent to a subscription, cancels, and then attempts to resign up, is the PI that was associated with the canceled subscription no-longer attatched to the customer, or does it remain attatched for future transactions? Currently, we are asking customers to re-enter payment info when they renew their subscription and logging that as a setupIntent.
I think we assumed that the PI was removed because it was associated with the customer's subscription and not the customer themselves...
Ah, as far as I know the Customer can still pay on the Payment Intent if the Invoice status isn't void
gotcha. Okay, this gives me some good info to use moving forward. Thanks!!!