#focux

1 messages · Page 1 of 1 (latest)

still spokeBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

bronze light
#

I was searching on the api reference and didn't find anything

woeful rampart
#

Hi 👋 you don't. Checkout Sessions are intended for collecting payment method details while processing a payment, if you don't need to collect payment method details you don't need to use Checkout.

#

What are you using Checkout Sessions to process, one time payments or Subscriptions?

bronze light
#

We are using standard connected accounts and have had some issues processing refunds so one of the support agents here suggested using direct charges with the connected account. We were using the checkout page to process one-time fee payments.

#

All our customers are on the principal stripe account, so to use direct charges I'm cloning the payment methods in the connected_account but now I need to use it.

woeful rampart
#

Gotcha, so for Direct Charges and one-time payments, there are likely two flows to follow, largely depending on whether or not you need an Invoice to provide your customer. If you do, you would want to create an Invoice, if you don't then you'll be working directly with a Payment Intent. Do you think you'll need an Invoice?

bronze light
#

I don't think I'll need an invoice but is there a way of doing this keeping the checkout session? Like, right now, even when we have the user's payment saved, we take them to the checkout session UI where they can see the descriptions and all details about the fee and then confirm the payment

#

That's how it currently works and we like that so if possible we would want to keep that experience