Product
ACH and pay by bank
In one line
Bank rails for the volume cards price badly.
Reviewed
In the product
Mandates, verification and returns in one view, so a return code is a line item rather than a mystery.
Returns · last 30 days
What it is
ACH is not a fallback. For large tickets, B2B invoicing and monthly service fees it is usually the better instrument: the cost per transaction does not scale with the amount, and the dispute regime is narrower than the card networks'.
It is not free of return risk. NSF returns, unauthorized-debit returns and administrative returns each behave differently and each has its own window, so authorization records matter as much here as compelling evidence does on a card dispute.
Capabilities
What you get, specifically.
Debits and credits
Pull payments from customers and push funds to vendors, contractors or distributors on the same rails.
Account verification
Bank account verification before the first debit, which is the single biggest lever on return rate.
Authorization capture
Written, recorded or click-through authorization stored against every mandate, because that is what an unauthorized-return challenge needs.
Return handling
Return codes surfaced with retry logic that respects NACHA limits rather than hammering an account.
Specification
The detail.
- Rails
- ACH debit and credit
- Verification
- Account verification before first debit
- Per-transaction cost
- Set at underwriting
- Settlement timing
- Set at underwriting
- Return rate thresholds
- NACHA standard
Rows reading set at underwriting are not omissions. Those figures are decided per merchant against your vertical, volume and history, and you will see all of them in writing before you sign.
Tell us what you sell.
Before anything sensitive changes hands, we will tell you whether one of our acquiring partners writes your vertical, roughly what the terms look like, and what underwriting will ask you for.