#masonhale-connect-express
1 messages · Page 1 of 1 (latest)
@restive chasm overall that is a correct read. The ways you work around it is to take a bigger fee to make up for those refunds, or you charge the refund separately, say monthly
Thanks @queen herald -- how would I "charge the refund separately?" when I can't make a negative transfer? How would I charge anything?
You can use Account Debits for example: https://stripe.com/docs/connect/account-debits
or take a bigger fee on future transactions, or charge them on a monthly fee on their card
@queen herald ok, that's very helpful. I didn't find Account debits in my search. Is there a reason I wouldn't use an Account Debit on a per-refund basis? Why the suggestion to do these monthly instead?
Mostly preference really, as you scale, your users might prefer one monthly debit other N debits throughout the month
@queen herald looking at the Account Debit docs I see this warning "Using Account Debits require getting legally binding consent from your connected accounts." How do I go about obtaining that consent? Is it not part of the Stripe account onboarding? If it is separate, how would I affirm to Stripe that I have obtained the required consent?
You would collect this yourself. It's the same way as if you collected their card details to debit them. I don't really have specific advice for it beyond that
Their card details are collected via the Stripe onboarding -- we never touched any debit/banking details or approvals related to that information.
I also see there are additional fees for Account Debits, I will need to do some more digging to figure out the costs of those...
Thanks for your help.
Sure what I meant is that you can collect their card details, save those under a Customer and then charge them monthly
Hmmm... okay. I'm not sure that will work for our customer base (volunteer run youth sports teams) as most don't have a team credit card. But it is an interesting option.