Thoth-checkout

[tight token]

hi! Checkout is a hosted page the customer visits to enter their payment details. I don't see what interaction it would have with an off-session payment your backend would trigger without the customer being there.

[waxen grove]

so you can't do recurring payments with checkout Right?

[tight token]

hmm, what does that mean though?

like you can use Checkout to start a subscription and collect the initial payment, and then the recurring payments happen automatically using our Subscriptions/Invoices products, that's completely supported

Checkout is not involved in the recurring payments themslves since those just charge the customer's saved card from the backend.

[waxen grove]

What's the need for the paymentsintent api then?

i am trying to add recurring payments to my app. It's a bit confusing which api to use

[tight token]

for doing a one time payment directly without using Checkout for whatever reason(either you have your own frontend web page instead), or for processing recurring payments directly if you're not using our Subscription and Invoice APIs

[waxen grove]

wdym for processing recurring payments directly?

isn't it processed directly when using checkout?

[tight token]

I mean if for example you want to run your own cron job and collect recurring payments by having your server call our API each month, instead of using our Subscriptions that charge automatically

[waxen grove]

oh i see

[tight token]

you can use Checkout to start a subscription and collect the initial payment, and then the recurring payments happen automatically using our Subscriptions/Invoices products

or you can not use any of that and build everything custom using PaymentIntents if you want

[waxen grove]

i thought paymentsintent api charged automatically

[tight token]

no, it charges when you call the API to confirm the PaymentIntent.

[waxen grove]

yeah i mean after the initial confirmation

does it charge automatically the next month?

[tight token]

I mean it depends.

A PaymentIntent itself is just a one time payment. You confirm it, it's done, that's it.

• If you created the PaymentIntent yourself, that's it, nothing happens next month unless you are creating another PaymentIntent then.

• If the PaymentIntent you confirmed is from the Invoice of a Subscription(i.e you are using latest_invoice.payment_intent per the guide at https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements for example) , then the PaymentIntent succeeding has the side effect of paying the invoice and activating the subscription, so the Subscription will be active and will automatically recur next month.

[waxen grove]

that makes more sense

Its just hard to understand the difference b/w the api's