ZenotiHelp

Configure ACH payments

ZTZenoti Docs Team Updated September 17, 2026 13 min readHow-to

ACH (Automated Clearing House) and its regional equivalents (Canada PAD, EU SEPA, Australia BECS / NPP) let your business collect bank-to-bank payments β€” both one-time charges and recurring membership debits. ACH is processed in batches and settles in 2 to 5 business days. This article covers enabling ACH on your processor, capturing customer mandates, choosing the right regional variant, and recovering from failures.

Important β€” ACH disputes are NOT defendable like card chargebacks. When a guest's bank issues an ACH return for an authorization-related reason (NACHA codes R07 Authorization Revoked, R10 Customer Advises Not Authorized, R29 Corporate Customer Advises Not Authorized), the funds are reversed and there is no Zenoti-mediated dispute mechanism comparable to card chargebacks. Before enabling ACH, confirm your business is willing to accept this risk profile. Mitigations are documented in Reduce ACH dispute risk.

Important β€” settlement timing is 2 to 5 business days. ACH is fundamentally slower than card payments. Invoices paid by ACH remain in a pending state until the bank confirms settlement. If your operations rely on instant invoice closure (e.g., service-completion gating, member entry control), evaluate whether ACH is suitable for that workflow before enabling it.

On this page

Why ACH

ACH offers two practical advantages over card payments for businesses that bill recurring memberships or accept high-value one-time payments:

  • Lower processing fees. ACH transactions cost less than card transactions in most processor fee schedules. For high-volume membership billing, the savings are material.
  • Stable mandate. Once a customer signs an ACH mandate, the authorization remains in force until the customer revokes it β€” there is no card-expiration churn.

The trade-offs:

  • Slower settlement (2 to 5 business days, longer over bank holidays).
  • Different dispute model β€” see the dispute-non-defendability callout above and Reduce ACH dispute risk.
  • Setup overhead β€” collecting and storing mandates is more involved than tokenizing a card.

Before you begin

Permission: EDIT (under Organization) β€” Required to enable ACH on a processor at the organization level. Permission: Manage Payments (under POS) β€” Required to capture a customer's bank account and mandate at the point of sale.

See Permissions for the full RBAC matrix.

  • Your organization must already have a payment processor configured (Adyen, Stripe Connect, or another supported processor that includes ACH support). See Set up a payment processor.
  • Your operating region must be supported by the processor for the specific direct-debit network you will use (US ACH, Canada PAD, EU SEPA, Australia BECS / NPP).
  • A bank account must be configured for receiving payouts. See Configure bank accounts for payments.
  • You should have read Track ACH payments so you understand the back-office monitoring side of ACH before enabling it for guests.

Enable ACH on your processor

The exact UI varies by processor; the steps below describe the general flow.

  1. At the organization level, click the Configuration icon.
  2. Search for and select Payment processor onboarding.
  3. Locate the integrated processor block for your processor (for example, Zenoti Payments (Adyen) or Zenoti Payments (Stripe)) and expand it.
  4. Look for an ACH or Bank Payments sub-section. The exact label varies by processor β€” for Adyen it is typically ACH Direct Debit, for Stripe it is ACH (US), for SEPA-region processors it is SEPA Direct Debit.
  5. Toggle the option on. The processor may require you to:
    • Re-confirm your bank account details for payout.
    • Submit additional KYC (Know Your Customer) documents (depending on jurisdiction).
    • Acknowledge the regional direct-debit terms (NACHA Originator agreement for US ACH; PAD payor authorization rules for Canada; SEPA mandate handling for EU; Direct Debit Request rules for Australia).
  6. Click Save.

Some processors do not expose ACH via the self-service onboarding screen and require a request through your account team. If the ACH sub-section does not appear in your processor block, contact Zenoti. Once enabled, the option becomes visible to center-level staff for capturing guest mandates.

Capture customer bank account and mandate

A mandate is the customer's signed authorization for your business to debit their bank account. Capturing a mandate has two parts: collecting the bank account details and recording the consent action.

Collect bank account details

Bank account details are collected through a processor-hosted form (Adyen Drop-In, Stripe Bank Element, or equivalent). The processor encrypts the routing and account numbers in transit; Zenoti does not store plaintext bank account numbers. The fields collected:

Field Format Notes
Account holder name Free text Must match the bank-account legal name.
Routing / sort / IBAN 9-digit ABA routing number (US ACH), sort code (UK), IBAN (SEPA), BSB (Australia) The format is region-specific; see Regional variants.
Account number Up to 17 digits (US), IBAN includes account in the IBAN itself, BSB-account separate (Australia)
Account type Checking / Savings US ACH only; SEPA / PAD / BECS do not require this distinction.

Record the mandate

Mandate consent can be captured in three ways depending on your operations:

  • Tablet e-signature. The guest signs on the iPad after reviewing the consent text. The signature is timestamped and retained with the mandate record.
  • Processor-hosted authorization page. The processor hosts a consent screen with regional regulatory text. The guest accepts; the processor returns a mandate reference to Zenoti.
  • Signed paper form (for businesses in regions where a wet-signature paper form is preferred). Retain the signed form per your jurisdiction's record-retention rules β€” typically a minimum of 2 years for US ACH; 14 months after mandate cancellation for SEPA.

The captured mandate is stored against the guest profile and is reusable for recurring debits. To revoke, contact your manager β€” guest-initiated revocation typically goes through the guest's bank, but the front-desk operator can also mark the mandate revoked in the guest profile to stop future scheduled debits.

Regional variants

The four direct-debit networks supported by Zenoti's processors share the same conceptual model but differ in regulatory specifics. Use the table below to choose the right variant and confirm the rules that apply to your business.

Region Network Regulator Mandate format Settlement window Dispute window
United States ACH NACHA NACHA-compliant authorization (electronic or paper) 2–5 business days; same-day ACH where supported by processor ~2 banking days for most return reasons; up to 60 calendar days for R07/R10/R29 (authorization-related)
Canada PAD (Pre-Authorized Debit) Payments Canada PAD agreement (CPA Rule H1-compliant) 2–4 business days Up to 90 calendar days for personal payors (consumer protection)
European Union (SEPA region) SEPA Direct Debit (CORE / B2B) European Payments Council SEPA mandate with Mandate Reference and Creditor Identifier 1–2 business days for B2B SDD; 5 business days for CORE SDD 8 weeks for unauthorized debits (CORE); shorter for B2B
Australia BECS Direct Debit (NPP for instant) Australian Payments Network Direct Debit Request (DDR) per the BECS rules 1–3 business days; NPP supports near-instant where the receiving bank is on-network Variable; refer to your processor's BECS rules summary
United Kingdom Bacs Direct Debit (where supported by processor) Pay.UK / Bacs Direct Debit Instruction with Direct Debit Guarantee 3 business days (Bacs cycle) Indefinite right of recall under the Direct Debit Guarantee

Configuration steps vary by processor β€” the Enable ACH on your processor flow describes the common pattern. For the regulator-specific consent text and document retention rules, refer to your processor's regional guidance and your business's legal counsel. Settlement and dispute windows above are summary references; processor-specific timelines may vary.

Use ACH for membership recurring billing

ACH is supported as a recurring-payment method for memberships through the batch processor. To set up an ACH-billed membership for a guest:

  1. Capture the guest's bank account and mandate per Capture customer bank account and mandate.
  2. Open the guest profile and navigate to Memberships.
  3. On the active or new membership, change the Payment Method from a card to ACH / Direct Debit / Bank Account. Select the previously-captured mandate.
  4. Click Save.

The next billing cycle will route through the ACH batch processor instead of the card processor. The first ACH debit on a new mandate may have a longer pending window while the bank verifies the account.

To switch existing card-billed members to ACH in bulk, contact your account team β€” bulk migrations are not exposed in the self-service UI in all processor configurations. Members who decline to provide bank details remain on card billing; there is no all-or-nothing requirement.

For membership billing rules, see the Memberships category.

Coexistence with card payments on memberships

Card and ACH coexist on the same membership cohort and even on the same individual member's history:

  • Per-member assignment. Each member can be billed by either a card or an ACH mandate. Different members in the same membership plan can have different payment methods.
  • Fallback ordering. When ACH fails (subject to retryable return codes β€” see Failure and dunning), the dunning processor can attempt the next configured payment method per the configured retry rules. If a guest has both ACH and a card on file, the system can fall back to the card; if only ACH is on file, the system retries the ACH per the retry schedule.
  • Switch direction. Members can switch from card to ACH or from ACH back to card at any time. The switch takes effect on the next billing cycle.

Settlement timing and invoice impact

Because ACH settles in 2 to 5 business days, the invoice paid by ACH does not close instantly the way a card-paid invoice does:

  • The invoice transitions to an ACH Pending state at the time the payment is initiated. Service can be rendered, but the invoice is not formally closed until the ACH settlement is confirmed.
  • The front-desk operator sees the invoice in a pending list until settlement. The pending status should not block the guest from booking new appointments unless your organization has explicit configuration to that effect.
  • Reporting reflects the service date for accrual-based reports and the payment date for cash-based reports. Mixed-basis reports must be filtered by the relevant date.
  • The invoice closes automatically when ACH transitions to a successful settled state. If ACH fails or is reversed, the invoice reopens and follows the standard failed-payment retry flow.

For details on tracking pending and settled ACH transactions, see Track ACH payments.

Failure and dunning

When an ACH transaction fails, the receiving bank issues a NACHA return code (or its regional equivalent). The system surfaces the return code and dispatches the next action based on the code:

Return code Reason Action
R01 Insufficient funds Account does not have enough funds Dunning processor retries per the configured retry schedule.
R02 Account closed Account has been closed No retry β€” the front-desk operator is alerted to contact the guest for new bank details or a card.
R03 / R04 Invalid account Account number error No retry β€” alert the front-desk operator to verify and re-capture bank details.
R07 Authorization revoked Guest revoked their mandate No retry β€” mark the mandate revoked. Contact the guest before any further attempts.
R08 Payment stopped Guest placed a stop-payment No retry. Contact the guest.
R10 Customer advises not authorized Guest disputes the debit No retry β€” high dispute risk. See Reduce ACH dispute risk.
R29 Corporate customer advises not authorized Corporate account-holder dispute Same as R10.
Other Bank-side or technical error Dunning processor retries per schedule.

Retry schedules are configured under Configure recurring payment rules. Authorization-related codes (R07, R10, R29) bypass the retry schedule entirely β€” these require human intervention.

The guest is notified of failed payments through the existing payment-failure notification channels (email, text, in-app β€” same channel pattern used for card-payment failures). The front-desk operator gets an alert in the failed-payments list for the center.

Reduce ACH dispute risk

Because ACH disputes are not defendable through the standard card-network chargeback flow, mitigation has to happen before a debit, not after. Apply these practices:

  • Verify bank routing and account numbers at mandate capture. Use the processor's micro-deposit verification flow if available β€” a small test deposit followed by a confirmation step proves the guest controls the account before any production debit.
  • Use processor-hosted consent forms. The regulatory consent text is correctly worded for the region, reducing the chance of a successful R10 dispute.
  • Retain mandate records per your jurisdiction's retention rule (US: 2 years minimum; SEPA: 14 months post-cancellation; Canada PAD: per CPA Rule H1; Australia: per BECS rules).
  • Set guest expectations during opt-in. State the debit amount, frequency, and how the guest can revoke the mandate. The opt-in screen is a good place β€” do not bury this in fine print.
  • Refuse ACH for guests with prior R07/R10/R29 returns. A returned authorization-related debit is a leading indicator of future returns. Maintain a list and decline future ACH mandates from those guests.
  • For high-value transactions, prefer card payments. ACH is best for recurring membership billing where the dispute risk is small per cycle. One-time high-value charges are often better routed to a card.

Processing fees

ACH processing fees are processor-dependent and are not exposed in Zenoti as a static configuration value. Fees vary by processor, region, and your specific contract terms. Contact your Zenoti account team for fee information applicable to your organization.

Permissions

Action Permission required
Enable ACH on a processor (org-level) Organization > EDIT
Capture a customer bank account and mandate (center-level) POS > Manage Payments
View ACH transaction status and failures Reconcile Payments (under Payments)
Process an ACH refund Refunds > EDIT
Reverse or void an ACH transaction (within reversal window) Refunds > EDIT AND ACH > Reverse

For organizations with custom roles, your administrator can configure these permissions per role through the standard role-management surface at Configuration > Security > Security roles.

Tips

  • Enable micro-deposit verification before going live. Confirming account ownership before the first production debit significantly reduces R10 and R29 returns. Ask your processor account team whether micro-deposit verification is available for your region and processor configuration.
  • Stagger your first ACH billing run. When migrating a large membership cohort from card to ACH, run a small pilot group first (10–20 members). Monitor the return codes over the first two billing cycles before migrating the full cohort. This limits exposure if routing or account numbers were captured incorrectly.
  • Configure dunning rules for ACH separately from card rules. ACH failures incur reversal fees; keeping the number of retry attempts low for ACH (especially for authorization-related codes) reduces your cost exposure. See Configure recurring payment rules for the ACH-specific dunning settings under Change status of recurring collections when payments from direct debit fail.
  • Use the payment dashboard to monitor ACH batch status. The payment dashboard shows pending, settled, and failed ACH transactions. Filter by payment type to isolate ACH activity and identify batches that have not settled within the expected window. See Track ACH payments.
  • Document your mandate revocation process. When a guest requests mandate revocation, the front-desk operator should mark the mandate revoked in the guest profile immediately β€” before the next billing cycle runs β€” to prevent an R07 return.

Troubleshooting

Problem Likely cause Resolution
ACH sub-section does not appear in the processor onboarding screen ACH is not enabled for your processor configuration or region Contact Zenoti. ACH availability depends on your processor contract and region. The sub-section only appears after ACH is activated on the processor side.
Guest's ACH payment is stuck in pending for more than 5 business days Bank holiday delay, processor batch timing, or the receiving bank is slow to respond Check the payment dashboard for the transaction status. If the status has not updated after 7 business days, contact your processor's support team with the transaction reference number.
R03 or R04 return code received immediately after mandate capture Routing number or account number was entered incorrectly Contact the guest to re-capture their bank account details. Use the processor-hosted form to reduce manual entry errors. If available, enable micro-deposit verification to confirm account details before the next debit.
R07 or R10 return code received on a recurring membership debit Guest revoked their mandate or disputes the authorization Do not retry. Mark the mandate revoked in the guest profile. Contact the guest to discuss an alternative payment method (card or a new ACH mandate with fresh consent). See Reduce ACH dispute risk.
ACH option does not appear when setting a membership payment method ACH has not been enabled at the processor level, or the guest does not have a captured mandate on file Confirm ACH is enabled per Enable ACH on your processor. Then confirm the guest has a valid mandate captured in their profile before attempting to assign ACH as the membership payment method.
Invoice remains open after ACH settlement window has passed The ACH batch did not receive a settlement confirmation, or the transaction was returned Check the payment dashboard for the transaction's current status. If the status shows a return code, follow the return-code guidance in Failure and dunning. If no status update is visible, contact your processor.
Was this article helpful?
Your feedback helps us improve our documentation.