ACH Payments for Membership Sites

ACH lets a membership site pull dues straight from a member's US bank account, which suits recurring, larger or yearly payments. To do it, you need three things: a processor that supports recurring bank debits (such as Stripe ACH Direct Debit or Plaid Transfer), a verified bank account, and the member's written or online authorization, called a mandate. ACH is slower than cards and members can dispute debits for up to 60 days, so plan for failed payments before you switch.

This guide is general information, not legal or financial advice. Talk to your processor or a payments lawyer about your exact setup.

Why use ACH for memberships?#

ACH makes sense for memberships when payments are recurring, larger, or paid by members who prefer to pay from a bank account. Stripe's ACH Direct Debit docs (opens in a new tab) say ACH "is popular for businesses with large or recurring transactions" and has lower costs than Stripe's instant bank option. As listed on stripe.com/pricing (opens in a new tab) on October 23, 2026, Stripe's ACH Direct Debit is 0.8% with a $5.00 cap.

The tradeoffs are real, though:

What are your options on WordPress and MemberPress?#

You have three main ways to take recurring ACH on a WordPress membership site: use your gateway's built-in bank debit, link with Plaid and pay through a processor, or move money with Plaid Transfer.

First, check what your membership plugin supports. MemberPress's gateway guide (opens in a new tab) lists Offline, Stripe, Square, PayPal Standard and Authorize.net, plus PayPal Commerce and manual transactions in its tutorials. The guide does not mention ACH or bank debit, and it lists "3rd Party Gateways" as "unsupported by our team." So before you promise members a bank payment option, confirm it works with your exact gateway and plan.

Then pick a money route:

How do recurring ACH payments work with Stripe?#

Stripe ACH Direct Debit supports recurring payments through Stripe Billing and saved payment methods. Stripe's ACH docs (opens in a new tab) describe the key rules:

1. The member authorizes the debit. Stripe shows and records the mandate for you in Checkout, the Payment Element and the hosted invoice page. In a custom form, you must show the mandate text yourself.
2. The bank account is verified. Stripe uses Financial Connections for instant verification, or micro-deposits if the member types the numbers by hand. Members have 10 days to confirm micro-deposits.
3. Stripe emails the mandate. Nacha rules require you to give each customer a copy of the mandate, and Stripe does this by default when you have a billing email.
4. Payments settle. Standard settlement is T+4. Eligible US businesses can turn on T+2.
5. Failed payments can retry. Stripe can automatically retry a failed ACH Direct Debit a maximum of 2 times, no more than 40 days after the original attempt, and does not charge debit failure fees for those automatic retries.

Stripe also lists two rules that matter for recurring billing. If you originate recurring preauthorized debits, you must disclose how amounts are calculated or the range members can expect. And you must give at least 7 calendar days notice if you change the timing of those debits.

How do recurring transfers work with Plaid?#

Plaid Transfer has a recurring transfers feature that originates fixed-amount ACH debits on a schedule you set. Per Plaid's recurring transfers docs (opens in a new tab):

1. Create the schedule with /transfer/recurring/create. You set an interval in weeks or months. Weekly schedules pick a weekday (1 to 5 for Monday to Friday). Monthly schedules pick a day from 1 to 28, or count back from the month's end (-1 is the last day).
2. Set an optional end date. Without one, the schedule runs until you cancel it.
3. Watch the webhooks. RECURRING_NEW_TRANSFER fires when a debit originates, RECURRING_TRANSFER_SKIPPED when an authorization check fails, RECURRING_CANCELLED when the schedule ends early, and TRANSFER_EVENTS_UPDATE for each transfer's status.
4. Cancel when a member leaves with /transfer/recurring/cancel. Canceling on the day a debit is due may not stop that debit.

Three details are easy to miss:

• Skipped is final. Plaid says: "If a recurring transfer instance is skipped due to a failed authorization check, it will not be retried." Your site needs its own dunning step, such as an email asking the member to update their bank.
• Weekends and holidays move the date to the next banking day, but only if that day is on or before the end date.
• Bank consent can expire. Plaid notes that at institutions that enforce consent expiration, such as Chase, consent may last as little as six months. Send the member through Link update mode before consent runs out so the schedule keeps working.

Plaid Transfer is US only, and you must complete the Transfer Application and be approved before going live, per the Transfer docs (opens in a new tab). Refunds can be partial, up to 10 per transfer, within 180 days of the original transfer, according to the Transfer refunds docs (opens in a new tab).

What do Nacha rules require for online membership debits?#

Nacha, which writes the rules for the ACH network, requires online (WEB) debit originators to validate the account and to have fraud monitoring processes. Here are the three rules a membership site is most likely to meet:

Nacha says account validation can be done with prenotifications, micro-transactions, validation services or API-based tools. Ownership checks are not required by the minimum standard, though some originators may need them. Phase 2 of fraud monitoring removes the volume threshold, so it covers non-consumer originators of any size. Nacha also says the rules do not require screening every entry one by one or before it is processed.

In plain terms: verify each member's account before the first debit, have a written process for spotting fraud, and do not store raw account numbers on your server.

How can you cut failed membership payments?#

You cut failed ACH payments by checking the account and the funds before you debit. These steps come from the tools in Plaid's and Stripe's docs:

1. Verify the account first. Use instant verification (Plaid Auth or Stripe Financial Connections) instead of typed numbers where you can.
2. Confirm the owner. Plaid's Identity (opens in a new tab) product can check that the account owner's name matches the member, which Plaid suggests before ACH transfers.
3. Check funds or risk before each debit. Plaid's Signal docs (opens in a new tab) describe Signal Transaction Scores, which estimate the chance a US ACH debit will be returned, and real-time Balance checks.
4. Report outcomes back. Plaid recommends reporting ACH returns so Signal can suggest better rules.
5. Tell members about refunds. Stripe warns that a refund does not stop a dispute, so tell members when you refund them to avoid a double credit.
6. Plan for blocked accounts. Stripe may block a bank account after certain returns, and sends a payment_method.automatically_updated event so you can contact the member before the next debit.

A simple rollout plan#

If you want to add ACH to an existing membership site, follow these steps in order.

1. Pick your route: Stripe ACH Direct Debit, Plaid plus a processor, or Plaid Transfer.
2. Check your membership plugin supports that route for recurring billing.
3. Write your mandate and terms, including how amounts are set and how members cancel.
4. Test in Sandbox or test mode with fake accounts, including failed and disputed debits.
5. Set up webhooks so your site updates access when a payment fails, is disputed or is refunded.
6. Write down your fraud monitoring process and a yearly review date, to match Nacha's Phase 2 rule.
7. Launch to a small group first, then open it to everyone.

Where does BankBridge fit?#

BankBridge is a WordPress plugin that connects your site to Plaid. It is built to work with WordPress, WooCommerce, Elementor, MemberPress and more, so you can bring Plaid's bank linking into your membership signup. You use your own Plaid account, and Plaid bills its fees to you separately.

For how it works with membership plugins, check the BankBridge docs, starting with the MemberPress guide, Plaid Link setup and Webhooks. You can also read our bank account verification for WordPress guide or see the BankBridge product page.

Sources#

Checked October 23, 2026.

• Stripe ACH Direct Debit documentation (opens in a new tab)
• Stripe pricing (opens in a new tab)
• Plaid Transfer (opens in a new tab)
• Plaid recurring transfers (opens in a new tab)
• Plaid Transfer refunds (opens in a new tab)
• Plaid Auth (opens in a new tab)
• Plaid Signal (opens in a new tab)
• Plaid Identity (opens in a new tab)
• MemberPress: choosing your gateways (opens in a new tab)
• Nacha: Supplementing Fraud Detection Standards for WEB Debits (opens in a new tab)
• Nacha: Fraud Monitoring Phase 2 (opens in a new tab)
• Nacha: Supplementing Data Security Requirements (opens in a new tab)

Plaid is a trademark of Plaid Inc. BankBridge is an independent plugin and is not affiliated with or endorsed by Plaid.