#ironbeard

1 messages · Page 1 of 1 (latest)

hybrid arrowBOT
shrewd moat
#

Hi there

floral shell
#

heyo 🙂

shrewd moat
#

Yep Subs will only be incomplete as an initial status on creation if they aren't trialing or active. They will never move from another status (like active or past_due) to incomplete.

floral shell
#

Gotcha. But can I depend on an upgraded sub to be past_due?

#

Looking at my reference, I guess the options are only incomplete, incomplete_expired, trialing, active, past_due, cancelled or unpaid.

So I guess only active, past_due, and upaid would work for this situation. I guess it's more important to me to know that an upgraded sub won't be active before the payment processes.

shrewd moat
#

Yes that's correct.

#

Since when you upgrade a new invoice will be generated, and if that invoice is not paid then the Sub will not be active

#

Are you using a send_invoice collection method?

#

Or why is the upgrade not being paid immediately?

floral shell
#

Hmm, the upgrade is not being paid immediately because..

#

I think it's cuz proration_behavior='always_invoice' and billing_cycle_anchor='now'

#

(this is the desired behavior..they put an upgrade in their cart and go to checkout page and confirm the upgrade once they see a prorated invocie)

shrewd moat
#

Nah that would just generate a new invoice. Can you show me an example Sub? Do you have a PaymentMethod set as the default for the Sub or Customer?

floral shell
#

sure one second

#

The customer ID is cus_MmbAVhCvcnE15y

#

I initially bought the "Major Metros" subscription, then later upgraded it to the "All Texas Regions" subscription

#

If you need more specific request ids, let me know

shrewd moat
#

Ah okay so you are actually setting "payment_behavior": "default_incomplete", on your update.

#

Do you not want to attempt to charge immediately on update?

floral shell
#

Ahh, yes that's right.

No, I want them to confirm their upgrade as if it were a normal checkout situation

shrewd moat
#

Hmm okay that still doesn't really make sense to me :). Like you should just wait to actually perform the update until they confirm they want to do so.

floral shell
#

But I guess I wanted to know if I can detect if it was upgraded by examining the status

#

hmm

shrewd moat
#

But that's fine. In your flow right now the Subscription will always move to past_due on update until you confirm the PaymentIntent

floral shell
#

Yeah, I think it's because my flow involves sending the client_secrets to the front end the same time the Card Element is displayed