#alex.esch

1 messages · Page 1 of 1 (latest)

brisk cometBOT
digital rock
#

That example uses Subscriptions, but same parameters apply to Checkout

violet sierra
#

hello, thank you

#

@digital rock
but, we are using payment intent with stripe elements right now
in case of migration to checkout, we will be not able to use custom workflow?

#

our goal is to have products inside payments, so we can calculate MRR

#

what is the best solution in your opinion?

#

we would like to preserve the current custom checkout flow

digital rock
#

Well if you're calculating MRR then that would suggest you have a recurring payments business?

#

So you'd be using Billing/Subscriptions, not Payment Intents directly

violet sierra
#

we are using both of them

digital rock
#

And they do support Products/Prices, unlike Payment Intents

violet sierra
#

in both cases we are using payment intents

#

so, when new subscription should be placed, we are creating new subscription, what's fine

#

but also we are selling bundles. which contains

  • kit (product)
  • list of apps (products)
  • shipping (product)
  • membership (subscription)

right now, everything is being managed by payment intent

#

so it looks like

#

we would like to have products inside payments

digital rock
#

Yep, one-time Payment Intents don't support line items and Products/Prices

#

Not without Checkout anyway

violet sierra
#

so.. as orders are deprecated, we can only use checkout, but it will be not a custom solution, but checkout based

#

right?

#

checkout based, means all ui will be provided by your side, and it will be hosted on custom domain

digital rock