#Apk

1 messages · Page 1 of 1 (latest)

cobalt barnBOT
thorn mulch
misty copper
#

So no need to specify any capabilities at all for standard?

thorn mulch
#

Correct

#

Payment methods are enabled/requested in the account's dashboard

#

You should have card_payments by default if you just onboard the standard account

misty copper
#

transfers as well by default?

thorn mulch
#

Why do you need transfers?

misty copper
#

I'm not sure, the docs just said if I'm using direct charges for my connected accounts (I'm charging their customers "on behalf of" them), that I'd need both card_payments and transfers

thorn mulch
#

But yes you should have transfers by default

misty copper
#

Awesome, thanks! Makes my code a bit cleaner not having to include those 🙂

thorn mulch
#

Gotcha

#

Yeah they should come hand in hand

misty copper
#

Is it possible to create the charge and THEN make a page for it?

#

So I know the charge's ID before I make a payment page?

thorn mulch
#

Not with Checkout

#

You'd need to create your own custom checkout page that you host to do that

misty copper
#

Yeah I'm trying to keep everything with Checkout and not custom for minimal code

thorn mulch
#

Yeah that's fine. That's what Checkout is great for

misty copper
#

For creating a checkout page (looking at the .NET examples), what is the difference between setting the Connected AccountID in PaymentIntentData.OnBehalfOf
versus puting it in RequestOptions.StripeAccount ?

thorn mulch
#

PaymentIntentData.OnBehalfOf is an entirely different concept meant to be used with destination charges

#

If you're focused on direct charges, then just set RequestOptions.StripeAccount

misty copper
#

Got it! Thanks, you can close this.