How to Accept eCheck Payments on WordPress

Short answer: to accept eCheck payments on a WordPress site, you add a payment gateway that can send ACH debits, show the customer clear authorization wording, verify their bank account on first use, and wait a few business days for the payment to clear. In WooCommerce that is usually Stripe ACH Direct Debit, an Authorize.net eCheck plugin, or Plaid with a processor. On the pricing pages we checked on 24 October 2026, eChecks cost 0.75% to 0.8% per payment, against 2.9% + 30¢ for a card on Stripe, which is why they matter most on large orders and recurring bills.

What is an eCheck?#

An eCheck is a payment where the customer authorizes your business to pull money from their checking or savings account, and the payment travels over the ACH network instead of a card network. Authorize.net calls it "a digital version of a paper check". In Nacha's language, an eCheck taken on a website is a WEB debit: a consumer debit authorized over the internet.

Three terms you will see in gateway settings:

• Routing and account number: the two numbers that identify the customer's bank account.
• Account validation: checking that the account is real, open and can take ACH entries, before the first debit.
• Return: the customer's bank sending the payment back, with a reason code, after it looked complete.

Why offer eChecks at all?#

Because card fees grow with the order, and ACH fees mostly do not. Using the public prices on Stripe's US pricing page:

That is the cost of doing nothing for a store with high-value orders, invoices or memberships: every large order paid by card carries a fee that a bank payment would cap. Verification adds a small amount: Stripe lists $1.50 per instant verification and free micro-deposit verification.

The trade-off is speed and certainty, covered below. eChecks are a poor fit for cheap impulse purchases shipped the same day, and a good fit for big tickets, B2B invoices, tuition, rent, donations and subscriptions.

What are your options on WordPress?#

All three move the money over the same ACH network. The difference is how the account is verified at checkout, which checks run before you ship, and how much custom work you take on.

How to accept eCheck payments, step by step#

1. Pick the gateway route. If you already use Stripe, start with Stripe ACH Direct Debit. If you use Authorize.net, turn on eCheck there. If you need bank login with risk checks across several plugins, look at Plaid.
2. Turn on the payment method. In Stripe, ACH is enabled under Payment Methods, then shown by the WooCommerce Stripe Gateway. In Authorize.net, eCheck is an add-on to the gateway plan.
3. Add authorization wording at checkout. The customer must agree to the debit. Say the amount, the date or schedule, and how to cancel. Plaid's docs point to the 2025 Nacha Operating Rules, section 2.3.2, for online authorization language.
4. Verify the account on first use. Nacha has required this for WEB debits since 19 March 2021: the system must "at a minimum, validate the account to be debited". A bank login, micro-deposits or a prenote all qualify.
5. Keep proof of authorization. Plaid tells Transfer users who collect their own authorization to store it for at least two years. Most gateways keep a record, but your own copy helps with disputes.
6. Decide when to ship. Hold the order until the payment clears, or ship earlier only after checks such as a real-time balance check.
7. Test the failure paths. A payment that fails, a return two days later, and a refund.

What should the authorization wording say?#

Clear wording protects you twice: it is required for an ACH debit, and it is your best defence when a customer later claims a debit was unauthorized (return code R10, which can arrive up to 60 days later). Plaid's documentation points merchants to the 2025 Nacha Operating Rules, section 2.3.2, for online authorization. In plain terms, the customer should see, before they confirm:

• that they are authorizing your business, by its legal name, to debit their bank account;
• the amount, or how it is worked out;
• the date of the debit, or the schedule for a subscription;
• how to cancel or revoke the authorization, and how much notice you need;
• a way to keep a copy, such as the order confirmation email.

A short example for a one-time order: "By placing this order, I authorize Example Store LLC to debit $249.00 from the bank account I selected, on or after today's date. I can contact Example Store at support@example.com to ask about this payment." For a membership, add the amount per period, the billing day and the cancellation route. Have your own adviser review the final text.

Common setup mistakes#

These are the problems that turn a cheap payment method into an expensive one:

1. Typed account numbers with no validation. This invites R03 and R04 returns and fails Nacha's first-use rule unless you validate another way.
2. Shipping before the return window passes on high-value physical goods.
3. A vague bank statement description. Plaid recommends describing what the payment is for in a few characters, because customers who do not recognise a charge dispute it.
4. No plan for failed renewals. Decide in advance whether a member keeps access while a returned debit is retried. Plaid only allows retries for R01 and R09 returns, up to two times.
5. Using a business SEC code for consumers. Plaid warns that debiting a consumer with a business code can be returned for up to 60 days with R05.

How long does an eCheck take?#

Expect a few business days. Authorize.net says processing "typically takes three to five business days". Stripe says ACH Direct Debit "can take up to 4 business days to receive acknowledgement of success or failure".

ACH only runs on banking days. Plaid's documentation lists the processing windows it uses: three Same Day ACH windows that settle the same day if submitted by 8:20 AM, 12:50 PM or 3:00 PM Eastern, and a standard window at 8:30 PM Eastern that settles the next morning. If you need money faster than that, read Can you accept ACH payments instantly?.

What can go wrong after the payment "clears"?#

An ACH debit can be returned after it settles. Plaid's returns documentation gives the two windows that matter:

R01 (insufficient funds) is, in Plaid's words, "by far the most common return type". Returns also count against you: Nacha watches unauthorized returns above 0.5% of your debits, and since Phase 2 of its fraud monitoring rule (19 June 2026, in practice 22 June) every business that originates ACH debits must run risk-based processes to spot fraudulent entries. The codes are explained in ACH return codes.

To keep returns low:

• verify the account before the first debit, not after;
• check the balance before large debits;
• use a clear statement description so the customer recognizes the charge;
• send a reminder before each recurring debit.

How BankBridge handles eChecks#

BankBridge adds Plaid's bank login to WooCommerce checkout and MemberPress signups, so the customer picks their bank and account instead of typing numbers. That covers Nacha's account validation in the same step. Before the debit, it can run Plaid Balance for available funds, Plaid Identity to compare the account owner with the buyer, and Plaid Signal for the chance of a return. The money then moves either through your processor, such as Stripe with a Plaid processor token, or through Plaid Transfer, as described in the WooCommerce doc.

You can try the bank connection in Plaid's Sandbox on the live demo, then pick a plan. Plaid bills its own fees to your Plaid account. If you only need Stripe ACH with micro-deposits, the free Stripe gateway plugin may be enough on its own.

This guide is general information, not legal or financial advice. Prices are from the providers' public pages on 24 October 2026 and change over time. Plaid is a trademark of Plaid Inc.; BankBridge is not affiliated with or endorsed by Plaid.