Electronic cheque · ACH-backed
topropay handles electronic-cheque acceptance through connected ACH partner processors under NACHA rules — hosted mandate capture, R-code-aware retries and one reconciliation feed alongside card and wallet receipts. The paper cheque retires; the buyer keeps the workflow they know.
Key benefits
Four properties that show up the moment paper cheque runs stop and the ACH partner batches start clearing on schedule.
Electronic check acceptance replaces the paper cheque lifecycle — no scanning, no bank deposit run, no lost mail. The buyer enters routing and account numbers through a hosted surface; the ACH debit clears in the partner processor's next batch.
The check-authorise endpoint mirrors the card-authorise endpoint shape. The merchant integrates once; adding electronic-cheque acceptance is a dashboard toggle, not a re-integration.
ACH returns fall into R-code categories (R01 insufficient funds, R03 account not found, R04 invalid account, others). The platform retries the recoverable classes on a scheduled cadence and flags the terminal ones for merchant follow-up.
Cheque debits, card authorisations, wallet receipts and refunds normalise into one ledger. Daily exports tagged by rail, processor, currency and merchant reference for finance.
How electronic check payment system flow works
What happens between the buyer submitting routing / account numbers and the funds landing in the merchant's ledger.
The hosted surface renders the electronic-cheque option alongside card and wallet. The buyer enters bank routing and account numbers into a NACHA-compliant form.
The platform captures the NACHA mandate authorisation — buyer identity, amount, cadence — and stores it as evidence for the merchant. Mandate ID travels with the debit.
The ACH partner processor batches the debit into the next ACH cycle. Same-day ACH is available where the partner supports it and the buyer's bank participates.
Settlement lands 1–3 business days later for standard ACH, same-day for same-day ACH. Returned debits carry an R-code; recoverable classes retry, terminal ones surface to the merchant.
The unified ledger tags every cheque debit with mandate ID, R-code (if returned), partner processor and clearing timestamp. Daily exports feed the merchant's accounting system.
Main use cases
Five merchant shapes that benefit from adding electronic-cheque acceptance alongside card and wallet on the same platform.
Enterprise buyers who prefer bank-rail settlement over cards for high-ticket invoices; e-cheque acceptance replaces the paper mail cycle with a hosted pay link.
Recurring utility bills where a bank-account debit is the norm; NACHA mandate captured once, monthly debits scheduled server-side.
SaaS merchants offering an ACH-cheque option for annual invoices where the customer's finance team prefers ACH over card for interchange reasons.
Recurring donations and membership dues via electronic cheque, keeping the transaction cost lower than card for the non-profit's donor base.
Rent collection via ACH cheque debit — tenant mandate captured at lease sign, monthly debits scheduled through the platform.
Platform features
Twelve capabilities grouped into cheque acceptance surface, rails & routing, and operations & finance. Same-day ACH is a per-transaction toggle.
NACHA-compliant routing and account entry; PCI-adjacent posture (bank data, not card data).
Hosted fields the merchant can drop into their own billing surface.
Cadence-scheduled ACH debits under a single mandate captured at first pay.
Ad-hoc single debits with a per-transaction mandate for one-off invoices.
Debits ride licensed partner ACH processors under NACHA rules; multi-partner where the merchant needs redundancy.
Faster settlement for merchants who need faster cash-conversion; per-transaction toggle.
Recoverable R-codes retry on a scheduled cadence; terminal ones flagged for merchant follow-up.
Same authorisation contract; scheme detection routes card vs bank-rail per BIN or account entry.
Every mandate stored with buyer identity, timestamp and IP for scheme-side audit.
ACH returns and chargebacks share a queue with card chargebacks; per-vertical evidence-pack templates.
Refunds trigger reverse-ACH; every refund logs actor identity, reason and timestamp.
Debits, returns, fees and refunds normalised into one ledger tagged by rail and partner processor.
Industry relevance
topropay's e-cheque posture targets licensed merchants operating across the US, EU, UK, APAC and LATAM — B2B invoicing with counterparties who prefer bank-rail settlement, SaaS annuals, utility and municipal billing, non-profit dues, and property-management rent collection.
Trust & compliance
NACHA mandate handling for the cheque side, PCI Level 1 for the wider platform, and an audit-grade event log for every debit event.
Ready to retire paper cheques
A 30-minute e-cheque review covers the ACH partner processors relevant to your geographies, the mandate-capture surface, R-code retry policy tuned to your vertical, and a sandbox to test against before any commercial commitment.
Frequently asked
Definitions, R-code mechanics, cost tradeoffs vs card and the practicalities of running cheque acceptance alongside card and wallet on one platform.
Check payment systems on topropay refer to electronic-cheque (e-check) acceptance — the modern replacement for paper cheques. Buyers enter their bank routing and account numbers into a hosted surface; the platform submits the debit through a connected ACH partner processor under NACHA rules. Paper cheque scanning and remote deposit capture are separate services and are out of the platform's scope.
Check payment processing on topropay starts with the buyer entering bank details on a hosted or embedded surface, followed by mandate capture, batching to the ACH partner processor, and settlement 1–3 business days later (same-day where supported). Returned debits carry an ACH R-code; the platform retries recoverable classes and flags terminal ones for merchant follow-up. Reconciliation feeds into the same ledger as card and wallet receipts.
E check payment processing digitises the paper-cheque lifecycle. The buyer's bank details travel over an authenticated form; the ACH network moves the funds; no physical cheque is written, mailed, scanned or deposited. Traditional cheque handling still involves paper artefacts, remote deposit capture and a longer settlement cycle. topropay operates in the electronic-cheque space, not the paper one.
Electronic check payment processing rides on the ACH network in the US and equivalent bank rails (SEPA SDD in the EU, Bacs in the UK) elsewhere. The 'e-check' label is a legacy term for what the industry now calls ACH debit — the underlying rail and the NACHA rulebook are identical. topropay uses the terminology consumers still recognise while the underlying flow is a standard ACH debit.
The check payment gateway on topropay isn't a separate product — it's the same unified gateway that handles cards, wallets and other rails, with a check-authorise endpoint that mirrors the card-authorise contract. The merchant integrates once; adding electronic cheque acceptance is a dashboard toggle, not a re-integration.
The electronic check payment system captures a NACHA mandate at first pay — buyer identity, amount, cadence and authorisation. Recurring debits run against that mandate on the scheduled cadence; the mandate is retained for scheme-side audit. Cancellation is an operator-side action that stops future debits without invalidating the settled history.
Check payment processing companies on the connected panel are licensed ACH partner processors selected for the merchant's target geographies and volume profile. Their identities surface on settlement statements per NACHA rules; externally the merchant integrates against topropay's unified gateway and doesn't manage the ACH-processor relationship directly.
Check payment processing services on topropay bundle: hosted or embedded e-cheque acceptance, NACHA mandate capture and storage, ACH debit submission through connected partner processors, R-code-aware retries, same-day ACH where supported, refund via reverse-ACH, and reconciliation into the unified ledger. Card and wallet acceptance ride the same integration.
Yes. Online check payment processing on topropay works under the platform's sub-merchant model — the merchant inherits the platform's acquiring and ACH-partner relationships rather than holding a direct MID. This is the same model that makes card acceptance available to merchants without their own MID.
Understanding ACH check payment processing starts with two ideas: (1) the debit clears in batches, not real-time — standard ACH settles 1–3 business days later, same-day ACH settles same day when both banks participate; (2) failed debits return an R-code that classifies the reason (insufficient funds, account not found, invalid account, etc.). The platform's retry engine handles the recoverable classes automatically.
The platform automatically retries R01 (insufficient funds) and R09 (uncollected funds) on a scheduled cadence, since balances typically replenish. Terminal codes like R02 (account closed), R03 (no account), R04 (invalid account number) and R08 (payment stopped) don't retry — they surface to the merchant for follow-up with the buyer. Configuration is dashboard-editable per merchant.
ACH chargebacks (formal disputes filed by the buyer's bank) and ACH returns (technical failures) both flow into the unified dispute queue. Returns carry the R-code; formal chargebacks carry the buyer's stated reason and any evidence. Evidence-pack templates per vertical pre-fill mandate ID, timestamp, IP and the merchant's fulfilment record for representment.
Same-day settlement is possible for electronic cheques via same-day ACH where the merchant's partner ACH processor supports it AND the buyer's bank participates. Cut-off times apply per NACHA schedule. For merchants who need faster cash-conversion, same-day ACH is a per-transaction toggle with a slightly higher per-item cost.
Yes. For merchants outside the US, the equivalent bank-rail debit acceptance is SEPA Direct Debit (EU), Bacs (UK) and PayID / PayTo (AU). The mandate-capture, retry and reconciliation flow mirrors the US ACH path; the underlying rail is the local scheme. Some rails don't use the 'cheque' terminology but functionally serve the same use case.
Electronic cheque acceptance typically has a lower per-transaction cost than card — a fixed ACH per-item fee rather than interchange + scheme + acquirer fees. The tradeoffs: settlement is slower (1–3 business days vs T+1 to T+30 for card, depending on scheme), and the return-management workflow is different. For high-ticket B2B invoices the economics usually favour ACH cheque; for low-ticket consumer purchases, card is normally faster and simpler.
Related