#tristanoneil-bacws
lunar cradle
Can I provide you w/ the account id and customer that'll have all of the events in question?
If that works it's acct_1JUEzSJN3JKqPOBy and cus_KJPdSZkHy84Fw9
vague shale
let me have a look
pliant wedge
Hello! So this is the request you're asking about, right? https://dashboard.stripe.com/test/logs/req_hEaIGAcBhppf9W
lunar cradle
Yep, that's right
golden root
Hello! I'm just stepping in since @pliant wedge had to leave. Give me a minute and I'll be right with you
Okay, so from the request you sent over it looks like you're creating the subscription with payment_behavior: default_incomplete. When you use this payment behavior, we don't attempt any payment or transition the subscription out of the initial incomplete status unless no payment is required (it's a trial or a $0 first invoice). We talk about this here: https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior
You need to make an explicit call to confirm the Payment Intent created from the subscription separately and once it's successful the subscription will become active
We have a detailed guide on how to handle subscriptions with default_incomplete here as well: https://stripe.com/docs/billing/subscriptions/elements
If you're desired behavior is for the subscription creation to attempt payment immediately, you would want to use payment_behavior: allow_incomplete or error_incomplete