Skip to content
pluginloom

Integrations

Use BankBridge with MemberPress

Bank payments and account checks for MemberPress memberships with Plaid: recurring ACH options, consent expiry, failed debits and what to test first.

Last updated by the PluginLoom team

BankBridge is compatible with MemberPress, so members can connect a bank account through Plaid Link when they join. For recurring plans, the key questions are who moves the money each period and what happens when a debit fails.

What does MemberPress support on its own?#

MemberPress's gateway guide (opens in a new tab) lists Offline, Stripe, Square, PayPal Standard and Authorize.net as its gateways. It does not mention ACH or bank debit, and it lists third party gateways as unsupported by the MemberPress team. That is why a bank payment option for MemberPress comes from an add-on such as BankBridge.

How can recurring bank payments work with Plaid?#

There are two Plaid routes, the same as for one-time payments.

Plaid Transfer recurring transfersPlaid Auth + processor
Who runs the schedulePlaidYour processor's billing system
Schedule optionsAny number of weeks or months; weekday or day of monthThe processor's options
Failed debitPlaid sends RECURRING_TRANSFER_SKIPPED and does not retry that instanceThe processor's retry rules
RegionUS onlyDepends on processor

Plaid's recurring transfers docs (opens in a new tab) say a monthly transfer can run on day 1 to 28 or count back from month end, and that a date on a weekend or bank holiday moves to the next banking day.

Some banks make a user's consent expire. Plaid says that at banks that enforce it, such as Chase, consent may last as little as six months. If consent lapses, the connection stops working and renewals can fail. Plaid recommends sending the Item through update mode before consent expires. Watch for the PENDING_DISCONNECT webhook, which Plaid sends about 7 days ahead for US and Canadian Items (Items API (opens in a new tab)).

What do the ACH rules say about recurring debits?#

Recurring online debits carry duties. Stripe's ACH Direct Debit docs (opens in a new tab) summarize some of them: you need the customer's authorization (a mandate) before you debit, you must give them a copy, and you must give at least 7 calendar days notice if you change the timing of recurring debits. Nacha requires WEB debit originators to validate an account the first time it is used (Nacha rule (opens in a new tab)). Plaid Auth is one way to do that. This is general information, not legal or financial advice.

How do I set it up?#

  1. Install and activate MemberPress and BankBridge.
  2. Connect your Plaid keys and pick your route: Transfer, or Auth with a processor.
  3. Turn on the MemberPress integration in BankBridge settings.
  4. Choose which memberships offer bank payment.
  5. Add clear authorization text to the signup page that explains the amount, schedule and how to cancel.
  6. Set your webhook URL so status changes reach your site.

What should I test?#

  1. A new member signup paid by bank.
  2. A renewal. In Sandbox, fire the relevant webhooks to simulate it.
  3. A failed renewal, and what access the member keeps.
  4. A member who cancels, so no further debits are scheduled.
  5. A broken connection (/sandbox/item/reset_login) and the reconnect flow.

Sources#

Checked October 23, 2026.

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

Was this page helpful?