pelf-accss-connect | Stripe Developers | Page 1

safe barn Jan 10, 2022, 10:45 AM

#

yes you can not clone anything except cards. > Will this result in a direct charge?

#

argh too soon, one sec..

#

yes you can not clone anything except cards.

Will this result in a direct charge?

no, it's Destination charge with on_behalf_of. So it works like a Destination charge in that your platform is liable for the refunds/disputes/fees etc

The way to use a Direct Charges for ACSS and every other non-card method is just to create the PaymentMethods directly on the connected account(you can't use the model of accepting them on the platform and cloning them to the connected account). i.e. create the PaymentIntents with the Stripe-Account option, and use stripe.js with it as well https://stripe.com/docs/connect/authentication#adding-the-connected-account-id-to-a-client-side-application

violet matrix Jan 10, 2022, 10:50 AM

#

Thanks. Do I also need to pass the account id on the SetupIntent, or does that only apply to the PaymentIntent?

safe barn Jan 10, 2022, 10:51 AM

#

you have to pass it on the SetupIntent yes, sorry ,missed you said you're doing recurrring payments

#

you pass it on everything(Creating the SetupIntent, creating the Customer, etc) as that's what Direct Charges are, creating all the API objects on the connected account and not your own

violet matrix Jan 10, 2022, 10:55 AM

#

Ok, gotcha. So basically, I'm adding the connected account id in a header to ALL server side calls (creating customer, setup intent and payment intent) and act like I'm otherwise charging normally through our own account?

safe barn Jan 10, 2022, 10:57 AM

#

act like I'm otherwise charging normally through our own account?
not sure what you mean by that

#

but basically it's the same docs as https://stripe.com/docs/payments/acss-debit/set-up-payment but you pass Stripe-Account everywhere (including to stripe.js on the frontend for https://stripe.com/docs/payments/acss-debit/set-up-payment?platform=web#web-collect-mandate-and-submit (per the link I posted above) ) yep!

violet matrix Jan 10, 2022, 10:59 AM

#

Cool. I think I got it. Thanks for the help.

#

One more thing. I did a quick manual test using our staging environment, and I got a PaymentMethods of type "acss_debit" cannot be shared to a sub-account error when charging.
Is that because the account I tried to charge with was not an actual connected account? Does sub-account mean it's part of the same account somehow? (I'm not the one that set up those accounts, so I don't really know how it was done)

safe barn Jan 10, 2022, 11:07 AM

#

violet matrix One more thing. I did a quick manual test using our staging environment, and I g...

if you're getting that error then you must still be trying to share the PaymentMethod

#

so you need to change your code to not do that part if not charging cards, sounds like you need some branches in the code

#

I'd assume when you say "when charging" you are calling some function in your company's payment integration and the implementation of that function is trying to do cloning

violet matrix Jan 10, 2022, 11:13 AM

#

Oh, sorry that wasn't clear. This was before I talked to you. We were not yet passing the account id header everywhere.

So, the error is indeed related to us not doing the right thing then to direct charge to the connected account. Ok. I'll make the changes you suggested and will try again. Hopefully that makes that error go away. (Just wanted to make sure that wasn't because the accounts were not set up properly). The term sub-account threw me off.

#pelf-accss-connect