ACH collections & disbursements

Automate the money movement on funded deals - both pulling daily or weekly remittances and sending funds out at funding time.

Bank account tokens

Merchant bank accounts are stored as tokens from your connected payments provider, never as raw account numbers. Connect a provider under Integrations, then capture an account on the deal (via the merchant portal, a verification link, or manual entry).

Collections

Set a payment plan - amount, frequency, and start date - and the daily worker submits debits on schedule. Each attempt is posted to the ledger. Failed debits return with a coded reason (for example R01 insufficient funds) and can be retried automatically per your retry policy.

Re-pull a returned payment

On a bounced debit, Re-pull… lists the merchant's accounts and those of the deal's backup businesses; a person picks — nothing switches account on its own.

• The account that bounced re-presents the debit: not for returns that cannot be retried (R02, R03, R04, R07, R08, R10, R16, R20, R29, R31), at most twice by default, three days apart (both are company settings).
• Another account creates a pull dated today. After an authorization-revoked return (R07, R10, R29) the merchant's own accounts are refused until they re-authorize. A bounce already being re-pulled is refused.

Disbursements

When a deal is cleared to fund, initiate the disbursement to the merchant's tokenized account. The transfer is tracked end to end with its external transfer id and status.

Go-live safety

ACH money movement is dark by default for a new company. An administrator flips the per-company go-live flag once your provider credentials are verified, so no live debits run before you are ready.

Can’t find what you need? Return to the app or contact your administrator.