cabeedelhertz

[untold meadow]

Hello, do you have any IDs of subscriptions that this has happened with?

[frank nimbus]

sub_1OUMVRK7tk54C3dfOMVfpEWG
sub_1OmD3hK7tk54C3dfRidObR3s
sub_1LfqRFK7tk54C3df53XdgZ8P

[untold meadow]

Thank you, checking in to those

I am not sure what is happening here. I will check with my colleagued and get back to you on this one

@frank nimbus There is a fix for this. These retries aren't happening because your update calls are using a payment behavior of default_incomplete which sets auto_advance to false. So your two options here would be:

1. Make these update calls while passing allow_incomplete instead of default_incomplete
2. Make a second update call that specifically turns auto_advance to true after the call with default_incomplete

[frank nimbus]

interesting okay thank you. I have some logic that determines whether to set the payment behavior to either default_incomplete or allow_incomplete depending on whether the payment method in question has been set up for future usage already. The logic is that if the payment method has been set up for future usage, then the payment behavior is allow_incomplete, telling Stripe to attempt payment right away. And if the payment method has not been set up for future usage yet, then set the payment behavior as default_incomplete so we get the payment intent back and explicitly attempt to confirm the payment intent

[frank nimbus]

I put that logic in because otherwise, when someone was upgrading and providing a new payment method, if we set the payment behavior as allow_incomplete, then Stripe would automatically attempt the payment using the old payment method instead of the new.

is there a better way to force stripe to use the specific payment method when using the payment behavior allow_incomplete? I'm already setting the Subscription.DefaultPaymentMethod as the newly passed payment method, but Stripe would still charge the old payment method when using allow_incomplete

[untold meadow]

I am surprised to hear that. I will ask my colleagues and get back to you on that

[frank nimbus]

It specifically came up when I had a subscription originally paid for with a Card, and then I attempted to upgrade using Cash App. When I did so, Stripe would just charge the original card on file

[untold meadow]

Do you happen to have the ID of a specific subscription that you know has seen this behavior?

[frank nimbus]

We've since introduced the logic to use default_incomplete to avoid charging the old card, but I can spin something up locally to reproduce that. Will just be a few minutes

[untold meadow]

Apologies for the delay, still not finding anything on this other than setting the default payment method before making the other update. I think you should be able to do this with the invoice's /pay endpoint as well but I feel like there should be something within one API call.

[frank nimbus]

just tested with "allow_incomplete" with a Cash App upgrade and the backend errored because it requires a "return url". So I need to use "default_incomplete" when upgrading with Cash App

here is the request log https://dashboard.stripe.com/test/logs/req_jjmDtEZ6o3uzEd?t=1708984681\

[untold meadow]

Thank you

[frank nimbus]

So I think the default payment is working correctly, its just that new Cash App payment methods can't be used with "allow_incomplete"

[untold meadow]

Yep, I will check with my colleagues to see if we have a way to update subscriptions properly to use a cashapp payment method. Also I will make sure we improve that error, we shouldn't be telling you to pass in something that our API does not allow you to pass in for that call

[frank nimbus]

Would it work to update the invoice to have auto_advance: true later on, for example when I recieve an invoice.payment_failed webhook, or would I need to set that invoice attribute before the payment is attempted?

as an immediate / temporary solution ^ because ideally I could always just use allow_incomplete when upgrading a subscription if cashapp were behaving correctly

[untold meadow]

Yep, that is looking like the best way to handle for this for now. Updating using default_incomplete and then setting auto_advance to true after looks like the best way to go here with our APIs current capabilities

[frank nimbus]

okay thank you. Any idea on when we can expect the Stripe api to allow using allow_incomplete for new cash app payment methods?

[shy hamlet]

👋 Sorry for the delay! No, I don't have an ETA for when we'll support this flow.