HomeProduct DocsAPI ReferenceChangelog
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo
Product Docs
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo

ACH (US only)

Accept ACH bank account payments on Recurly for US merchants — with NACHA-regulated authorization requirements, dunning guidance, and support across Adyen, GoCardless, Stripe, Worldpay, and Check Commerce.

Tip You can try ACH in a sandbox environment before upgrading your plan.
ACH (Automated Clearing House) lets US merchants debit funds directly from a customer's bank account through Recurly. It's an alternative to credit card processing and physical checks, with support across five gateways. NACHA governs ACH authorization and bank account verification requirements.
Not included in Starter or Pro — contact Recurly Sales to upgrade
1Definition 2Checkout flow and settings

Prerequisites

Limitations

  • Available to US-based merchants only.
  • ACH has extended processing times and a multi-stage invoice lifecycle: pending → scheduled → processed. Each stage has its own implications and available actions.
  • ACH transactions cannot be voided via API — voiding is only supported in the Recurly Admin UI.
  • Automatic NACHA bank account verification is not available on all gateways. See the NACHA verification documentation for gateway-specific options.
  • 100% coupons during signup are not supported — e-mandate creation is required for this payment method. Use a free trial instead where supported. Standard coupons are supported.

Definition

ACH (Automated Clearing House) is a US payment method that lets Recurly merchants debit funds directly from a customer's bank account. It's governed by NACHA, which sets authorization and bank account verification requirements for all ACH transactions.

Checkout flow and settings

Payment authorization

ACH is regulated by NACHA, which defines the authorization merchants must obtain from customers before collecting payments. For bank account verification details, see the NACHA bank verifications documentation.

Merchants must collect the following from customers at the time of authorization:

  • Date of purchase
  • Amount of purchase
  • Customer name
  • Account number
  • Routing number and bank name
  • Authorization language for the payment and whether renewals will occur
  • Authorization language to attempt additional collections if the first transaction fails
  • Instructions for how and by when the customer must contact the merchant to cancel

Email communication

Customers receive email notifications at key stages of the payment process, keeping them informed of transaction status and next steps.

Dunning

ACH has longer processing times than card payments. Review your dunning length to confirm it's compatible with your Automatic Collection Dunning settings before going live.

Recurly settings

Hosted pages

Enable the Bank Account option in your Recurly site's Hosted Pages settings to accept ACH payments on hosted payment and invoice pages.

Webhooks

Update your webhooks to support ACH invoice state and payment state notifications. See the Webhooks documentation for implementation details and code samples.

API and Recurly.js

ACH is supported in Recurly.js v3 and API v2. See the API documentation and Recurly.js documentation for integration details.

Sandbox testing

Test your ACH setup on a Recurly sandbox site using the provided test credentials before going live.

Per-check limit

Keep your ACH payment threshold in sync with your gateway settings. To modify the threshold, contact your gateway. If issues persist, reach out to Recurly Support.

Updated 7 days ago

Did this page help you?