#johnroberts

1 messages · Page 1 of 1 (latest)

tiny breachBOT
brittle plank
dapper cypress
#

Thanks! If I do that, will the invoice be paid by a pull from the customer bank without the customer initiating it?

#

I was using 'send_invoice' as the collection method

brittle plank
#

It should, yes

#

I think it's ultimately up to you if you'd like to give the customer the option to use a different bank account for that second invoice

dapper cypress
#

Thanks. The behavior we want is to send an email for them to use to pay in each case, is that what would happen if we use charge_automatically? The example is a bar paying for a band booking at the end of the gig.

brittle plank
#

Ah got it. No, using charge_automatically will not send an email for them to pay

#

It sounds like send_invoice is what you want in this case. However, it's not possible to pull in the customer's prior payment details.

dapper cypress
#

We're replacing bar manager giving a paper check payment to band guy with an email to be paid by ACH

#

So the customer will go through the same bank connect process again? Is that instantaneous or does it take microdeposit verification?

brittle plank
#

Yes, the customer would go through the same connection process again.

dapper cypress
#

Ok, I will read up on that. Thanks for your help roadrunner! Any other recommended approach for what we are trying to do?

brittle plank
#

I think the tricky part is that your team would like to send invoices to customers every time (instead of automatically paying those invoices using a previously-used bank account)

#

For a future optimization, your team can look into asking customers to "opt in" to using previously-saved bank accounts for future invoice payments instead of sending them an invoice every time.