Separate ACH from card configuration
CMS Max enables Paya independently from the selected credit-card provider, so merchants can define bank-payment eligibility and operations without changing the card path.
Native ACH payment integration
Paya ACH for CMS Max
Give customers a bank-payment option with a separately controlled ACH workflow.
CMS Max integrates Paya as its native ACH and bank-transfer provider. It is enabled independently from the selected card gateway, uses a merchant terminal ID plus protected environment credentials, validates bank inputs, records provider transaction context, and supports settlement-aware void and refund operations.
- ACH bank transfer
- Separate from cards
- Sandbox + live
- Checking + savings
- Void support
- Refund support
with CMS Max
01Validate bank input
02Submit ACH debit
03Record reference
04Watch settlement
05Void or refund
Payment architecture
Treat ACH as its own tender and operating model.
ACH is not simply a less expensive card button. Bank inputs, authorization language, returns, settlement timing, customer expectations, provider risk rules, and reconciliation need a dedicated design.
Collect only the required bank data
The current Paya provider validates routing number, account number, checking or savings type, amount, and customer context before submitting the transaction.
Plan for delayed outcomes
Define settlement monitoring, bank returns, customer communication, order or service holds, void versus refund timing, reconciliation, and escalation with the provider.
Current capability boundary
A native ACH path built for CMS Max workflows.
Merchant approval, supported transaction types, account limits, timing, pricing, risk controls, and provider services are governed by the active Paya relationship and current configuration.
Independent ACH control
Turn on ACH without replacing the selected card gateway, then decide where bank payment appears across eligible CMS Max checkout or form experiences.
Terminal-based merchant setup
Enter the Paya gateway terminal ID in CMS Max while CMS Max uses the correct protected environment credentials for sandbox or production processing.
Structured bank inputs
Validate a nine-digit routing number, account number, checking or savings selection, amount, and relevant account-holder and billing context before processing.
Native Paya provider
CMS Max constructs and submits the Paya ACH request, interprets validation and result codes, records the provider transaction reference and token, and returns a clear outcome.
Settlement-aware action
The native provider supports void and refund behavior and can choose the appropriate path using the transaction timing and original token recorded by CMS Max.
Reconciliation and exception ownership
Monitor accepted payments, settlement, returns, reversals, provider errors, customer contacts, form or order status, and finance reconciliation under one policy.
Native ACH provider: Provider accounts, approval, pricing, services, availability, settlement, disputes, and production outcomes remain subject to the current merchant agreement, live configuration, and accepted implementation scope.
Responsibility matrix
Define the ACH contract from customer consent to settlement.
The CMS Max integration supplies the technical path; the merchant and provider supply account approval, policy, timing, legal language, risk decisions, and financial operations.
| Workflow area | Current boundary | Production acceptance evidence |
|---|---|---|
| Customer experience | CMS Max checkout or payment-enabled form | Eligibility, purpose, amount, authorization language, required fields, accessibility, errors, receipt, support, and privacy reviewed |
| Bank inputs | CMS Max validation plus customer-provided data | Routing number, account number, checking or savings, account holder, billing details, invalid and corrected input tested |
| Merchant identity | Paya terminal ID and environment-managed credentials | Approved account, correct sandbox or production values, restricted access, rotation and incident procedure documented |
| ACH processing | Native CMS Max Paya provider and Paya service | Success, validation failure, decline, duplicate submission, timeout, provider error, retry and customer outcome tested |
| Reversal | CMS Max void or refund path using original transaction context | Original reference and token, amount, timing, provider result, audit history, customer notice, and order or form update |
| Settlement and returns | Paya account plus merchant finance operation | Settlement report, bank returns, holds, service or fulfillment policy, refund timing, exception queue, and reconciliation owner |
Transaction lifecycle
Make the delayed bank-payment lifecycle visible.
An accepted request is not the same as final settlement. Preserve enough context for the merchant to explain and reconcile every outcome.
Offer
Present ACH only for the approved sites, forms, amounts, customers, products, or services under merchant policy.
Authorize
Collect bank and customer inputs with clear authorization language and validate required fields.
Submit
CMS Max sends the ACH transaction through the configured Paya environment and interprets the result.
Monitor
Store the transaction context and watch settlement, return, exception, customer, and operational status.
Resolve
Void or refund when supported, update the CMS Max record, communicate, and reconcile the provider and bank records.
Implementation sequence
Launch ACH with finance and operations at the table.
A bank-payment implementation needs more than credentials because settlement and return timing affect customer promises and fulfillment.
Confirm the Paya account
Verify merchant approval, terminal ID, supported ACH services, limits, settlement, returns, reserves, pricing, support contacts, and production activation with Paya.
Define eligible workflows
Choose the CMS Max checkout, invoice, donation, registration, bill-pay, or other form contexts that may offer ACH and document amount and customer rules.
Write customer and staff policy
Approve authorization language, privacy notice, receipts, fulfillment holds, service activation, cancellation, returned payment, refund, and customer-support procedures.
Configure and test sandbox
Use the correct terminal and environment credentials, then exercise valid and invalid routing or account inputs, amounts, account types, success, provider failure, and duplicates.
Test reversals and reporting
Prove original-reference storage, void and refund behavior, provider portal lookup, form or order updates, audit history, permissions, and finance reconciliation.
Accept live processing
Run a controlled production payment, observe the full settlement lifecycle, verify reports and bank activity, train owners, monitor failures, and record sign-off.
Operational ownership
Know who controls each payment outcome.
Clear boundaries make merchant onboarding, security, transaction support, refunds, disputes, incident response, and financial reconciliation faster.
- CMS Max
- Owns the native Paya provider, ACH settings and validation, checkout or form implementation, transaction context, supported reversal actions, and CMS Max support scope.
- Paya / Nuvei
- Owns merchant approval, provider credentials and terminal services, ACH processing, settlement and return records, provider availability, and provider support.
- Merchant finance
- Owns bank accounts, provider agreement, fees, reserves, authorization policy, settlement and return reconciliation, refunds, accounting, and access approval.
- Merchant operations
- Owns ACH eligibility, customer communication, order or service holds, exception response, staff training, support, and production acceptance.
Documentation and related resources
Verify current provider and CMS Max requirements.
Payment products, APIs, credentials, merchant services, networks, rules, and supported actions change. Confirm the live account and current documentation during implementation.
Payment integration FAQ
Resolve the practical questions before launch.
Turn each answer into configured rules, representative test cases, monitoring, written ownership, and production evidence.
Is Paya a credit-card gateway in CMS Max?
No. The current CMS Max architecture uses Paya as the native ACH and bank-transfer provider. Authorize.Net, CardPointe, or Stripe is selected separately for credit-card processing.
What does a merchant configure in CMS Max?
The merchant enables ACH and supplies the Paya gateway terminal ID. CMS Max uses the appropriate protected environment credentials for the configured sandbox or production service.
Which customer inputs does the current Paya provider validate?
The native provider validates a nine-digit routing number, an account number, checking or savings account type, amount, and optional account-holder and billing context.
Can Paya ACH be used in CMS Max forms?
Yes. The current CMS Max payment-form architecture maps ACH payment fields to the native Paya provider, subject to tenant configuration, merchant approval, form design, testing, and operational policy.
Does the integration support voids and refunds?
The native provider includes both actions and can use transaction timing to select a pre-settlement void or later refund path. Eligibility and final results still depend on the original context and provider state.
How much does Paya ACH cost?
Pricing, reserves, limits, settlement, and related account terms are merchant- and provider-specific. CMS Max should not publish a fixed rate; request current written terms from the active provider.
Is an accepted ACH request final payment?
Not necessarily. ACH has settlement and return behavior that differs from cards. Merchants should define holds, customer communication, return handling, reconciliation, and when fulfillment or service may proceed.
Build payment confidence
Connect payment technology to an operation the merchant can trust.
Bring the provider account, required tenders, checkout and form journeys, countries and currencies, refund policy, fulfillment rules, finance process, support owners, security requirements, and launch goals.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.