#CaReS
1 messages ยท Page 1 of 1 (latest)
it should be only
payment_intent.created
payment_intent.succeeded
charge.succeeded
customer.subscription.updated (status active)
Copying the other message here.
Hi! Let me help you with this.
Could you please share the Subscription ID? sub_xxx
sub_1Mg4OiABr9G9iqne5LRSc3fI
Hi, sorry for delay, I'm still looking.
ohh ok thank you
could be this ?
https://stripe.com/docs/billing/subscriptions/pending-updates
just tested, no it's not
Thank you for testing, still looking in to what this might be and will get back to you
thank you ๐
You will want to use payment_behavior=allow_incomplete when making these updates. Otherwise Otherwise we don't attempt to charge immediately and the subscription goes to past due for a few secs until you confirm the PI yourself https://stripe.com/docs/api/subscriptions/retrieve#create_subscription-payment_behavior
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
hmm
let me check
there is no difference with
payment_behavior=allow_incomplete
or without it
I got again two webhook with diference status
Interesting. Checking in to what else might help
Do you have the ID of that subscription?
Yep thank you
from code perspective it does
$user->updateDefaultPaymentMethod($paymentMethod);
$user->createOrGetStripeCustomer();
$subscription->incrementAndInvoice($quantity);
could some of this method recall update event ?
on subscription
Ah I did not notice that you are using Laravel Cashier here at first my apologies. I am unclear what that changes here but am looking
Ohh sorry about that I think I should say it at the first time (
hey sorry still having trouble figuring this out but I am still looking
Would you be able to send me the ID of the newer subscription that you tried the update with allow_incomplete? Or was that the same subscription?
was the same subscription
each my test are only on this subscription id
sub_1Mg4OiABr9G9iqne5LRSc3fI
gotcha thank you, checking in to this
Interestingly I still only see update requests with "payment_behavior": "default_incomplete", on that subscription. Is it possible that your latest code wasn't running when trying to update this subscription?
hmm not sure let me check once again please
seems there is not changes
I got two events again (
That still says default incomplete though?
Oh I see I said the wrong one
Sorry this second time I meant to ask you to double check that allow_incomplete was being set
I was trying with allo incomplete
and there is no changes
but let me check once again
I can still only see default_incomplete in your logs. At this point this may be a question of how to pass that value properly with Laravel Cashier
where I can check this logs?