#mrcoles

1 messages · Page 1 of 1 (latest)

warm fossilBOT
orchid flint
#

Hello! For #1, that's correct. For #2, no, if you follow the guide as-is the Customer is created regardless of submission. For #3, that's also correct, you can ignore incomplete Subscriptions.

raw sigil
#

Thx! Oh interesting—for #2 customer_creation="if_required" —the hosted checkout will create customers regardless of how far the person gets in the checkout?

orchid flint
#

No, Checkout should only create a Customer if the Checkout Session succeeds.

raw sigil
#

Oh sorry I mis-worded things in #2—your most recent answer matches how I was interpreting it. So there’ll potentially be a bunch more zombie Customer objects with the Payment Element approach (if I’m allowing unauthed users to create a sub), right? And maybe that’s fine?

orchid flint
#

Yes. As far as it being fine, it's fine from Stripe's end, but I can't tell you if it's fine for your use case or not. 🙂

raw sigil
#

Haha, thx

orchid flint
#

We do generally recommend Checkout, as there are a lot of advantages.

#

It would be a less complex integration, less code on your end, you get more updates and features "for free" as we improve Checkout, etc.

raw sigil
#

My problem is I want to support Scheduled Subscriptions and they don’t work with Checkout (as far as I’m aware)

orchid flint
#

Can you tell me more? What kind of scheduling do you want to perform?

raw sigil
#

Payment installments. Purchase 5 months for $100/mo

#

(also I have requests for larger up front payment that settles into a lower amount, e.g., something like $1000 first month, $0 2nd month, $100/mo after that)

orchid flint
raw sigil
#

But then doesn’t the customer see confusing language in checkout like “$100/mo in perpetuity” and that might spook people who are expecting it to be just for 5 months?

orchid flint
#

Yeah, it wouldn't be perfect. You can test it out in test mode and see what it would be like.