A customer only sees a debit land on their account after they have actually agreed to it, because the batch gets created the moment they text back to confirm they are ready to pay. That single reply is enough to trigger creating a batch of EFT debits inside Direct Debit, so nobody has to log in and build the batch by hand once a payment has been agreed over SMS.

Direct Debit also lets a Zap create a batch of EFT debits from a CSV file when a business needs to load many accounts at once, keeping that bulk collection step separate from anything a customer says by text. Connected through Zapier, Mobile Message supplies the inbound reply and Direct Debit turns it into a properly formed batch ready to submit, so a collections team spends less time re-entering account numbers that already sit in a text thread, and the customer only ever sees a debit they said yes to.