Apply securely
Use an authorized merchant representative and submit accurate legal, ownership, banking, website, product, volume, and policy information.
CMS Max Adds Paya ACH Payments for Websites and Forms
Native ACH payment path
Give customers an approved bank-payment option without confusing onboarding with launch readiness.
CMS Max includes a native Paya provider for eligible ACH and bank-transfer workflows. The merchant application begins the provider relationship; underwriting, terms, credentials, limits, settlement, returns, and production approval remain provider-controlled.
- Native ACH provider
- Secure application
- Controlled activation
- Settlement operations
Decision frame
Treat ACH as a complete payment operation.
The website experience, provider account, merchant policies, customer authorization, transaction state, settlement, returns, accounting, and support all need explicit owners.
Review the agreement
Confirm pricing, funding, reserves, limits, returns, termination, support, and compliance obligations in writing.
Accept production
Use matching environments and representative tests, then verify a controlled live payment, settlement, reversal policy, and sign-off.
Platform and operating capability
CMS Max connects approved Paya accounts to supported ACH workflows.
The verified provider is separate from the selected card gateway and can support eligible checkout and form payment contexts.
Native provider
CMS Max includes a current Paya payment provider for ACH and bank-transfer operations.
Terminal setup
The merchant supplies the approved gateway terminal while protected environment credentials support the provider service.
Input validation
The current implementation validates routing, account, account type, amount, and available customer context before submission.
Transaction context
CMS Max records provider references and outcomes with the relevant order or form payment operation.
Reversal paths
Supported void or refund behavior depends on transaction state, provider response, merchant terms, and accepted implementation.
Settlement ownership
The merchant reconciles provider deposits, returns, holds, fees, customer issues, and accounting.
Implementation workflow
Move from application to a reconciled live bank payment.
Do not place credentials or sensitive terminal details in public content or ordinary communication.
- 01
Prepare
Gather legal identity, ownership, bank, website, products, volume, fulfillment, refunds, and authorized contacts.
- 02
Apply
Submit accurate information through the secure hosted application and respond to underwriting questions.
- 03
Review
Accept only after reviewing the complete written provider decision, pricing, limits, funding, returns, and support terms.
- 04
Configure
Enable the approved Paya path in CMS Max with the correct terminal and matching environment, then exercise success and failure cases.
- 05
Accept
Run a controlled live payment, verify customer and CMS Max state, confirm settlement, test reversal policy, and record sign-off.
Practical reference
Assign ownership before sensitive merchant data is submitted.
The application is hosted on Maxforms; Paya or Nuvei controls the resulting merchant relationship and provider operation.
- Applicant
- Authorized merchant representative with accurate business and ownership information.
- Provider
- Underwriting, account terms, credentials, terminal services, processing, and settlement.
- CMS Max
- Native integration, protected tenant settings, payment context, and supported actions.
- Merchant
- Policies, account security, customer communication, returns, disputes, reconciliation, and compliance.
- Launch evidence
- Approved account, correct environment, representative tests, live transaction, settlement, and sign-off.
Evidence and next steps
Use current product and primary-source guidance.
Features, provider requirements, plans, policies, interfaces, and search guidance can change. Verify the live CMS Max implementation and current official source before release.
Frequently asked questions
Make the practical decisions before launch.
Use each answer to identify configuration, evidence, testing, monitoring, and ownership.
Is Paya native to CMS Max?
Yes. The current application includes a native Paya ACH and bank-transfer provider.
Does submitting the form guarantee approval?
No. Paya or Nuvei controls underwriting, approval, merchant terms, and production activation.
Is Paya the card gateway?
The verified CMS Max architecture uses Paya for ACH. Eligible card processing is configured separately.
When can live payments begin?
After provider approval, correct configuration, representative testing, operational acceptance, and production activation.
What should be reconciled?
Review CMS Max payment records, provider references, deposits, fees, returns, holds, customer issues, and accounting.
Add ACH only after the merchant and operating path are ready.
Start with the secure application, then connect approval, terms, configuration, testing, settlement, returns, reconciliation, and support.