#Bart

1 messages · Page 1 of 1 (latest)

solemn sageBOT
dark valley
lean plover
#

why are destination charges recommended? @dark valley

dark valley
#

Because Express accounts are controlled by the Platform, so the Platform assumes more responsibility over the charges. Also, with Express accounts it is more likely that the Platform will be the one interacting with the end customer so they should have all the Customer and Payment Method records

lean plover
#

But thats the thing, we dont want more responsibility, we just want to be protected from negative balances

#

how it works

Master -> Express Connected -> Charges Customer -> Application Fee

dark valley
#

In that case why did you not use Standard Accounts?

lean plover
#

I want to control when withdrawals are conducted and how much of a withdrawal is conducted

#

and i want the user to be able to enter their debit card for withdrawals and not just their routing number for easier registration

dark valley
#

In that case you assume some additional risk, as we outline in our docs here:

A connected Standard account is always ultimately responsible to cover negative balances. For Express and Custom accounts, the platform is ultimately responsible to cover negative balances.

lean plover
#

@dark valley is it possile to withdraw funds from the connected accounts debit card to cover any negative funds?

dark valley
lean plover
#

I saw that but ```params := &stripe.ChargeParams{
Amount: stripe.Int64(1500),
Currency: stripe.String(string(stripe.CurrencyUSD)),
}
params.SetSource("{{CONNECTED_STRIPE_ACCOUNT_ID}}")

ch, _ := charge.New(params)``` that will charge the balance of the account not the account bank account associated with the connected account

#

so if we charge an account for say $5 and they do not have $5 in their Stripe balance it wont charge them