Use an authorized applicant
Submit accurate legal, ownership, bank, website, product, volume, refund, and support information through the secure form.
Secure merchant onboarding
Apply for Paya ACH Payments
Begin provider underwriting with clear expectations for documents, approval, configuration, and launch.
CMS Max has a native Paya ACH and bank-transfer provider. The hosted application starts the merchant relationship; approval, pricing, limits, credentials, terminal services, settlement, returns, and production activation remain controlled by Paya or Nuvei and the merchant agreement.
- Secure hosted form
- Provider underwriting
- Native CMS Max ACH
- Controlled activation
Operating model
An application is the beginning of payment onboarding.
The merchant should understand data collection, account terms, credentials, testing, settlement, returns, and operational ownership before launch.
Review written terms
Confirm pricing, reserves, limits, settlement, returns, termination, support, equipment, and compliance obligations.
Separate approval from activation
Configure and test the native CMS Max Paya path only after provider approval and required credentials or terminal information are issued.
Current CMS Max capability
CMS Max can connect an approved Paya account to ACH workflows.
The current application treats Paya separately from the selected card gateway and supports eligible ecommerce and payment-form operations.
Native ACH provider
CMS Max includes a current Paya payment provider for ACH and bank-transfer workflows.
Terminal-based setup
The merchant supplies the approved Paya gateway terminal ID while protected environment credentials support the service.
Input validation
The current provider validates routing, account, account type, amount, and available customer context before submission.
Transaction context
CMS Max records provider references and outcomes with the order or form payment operation.
Void and refund paths
Supported reversal behavior depends on transaction state, provider result, merchant terms, and accepted implementation.
Settlement operations
The merchant reconciles provider settlement, returns, holds, fees, customer issues, and accounting.
Step-by-step workflow
Move from application to a reconciled live payment.
Do not place production credentials or terminal details in the public application copy or ordinary communication.
Prepare business details
Gather legal identity, ownership, bank, website, products, volumes, fulfillment, refunds, and authorized contacts.
Submit securely
Open the hosted Maxforms application and provide only accurate information through the approved form.
Review provider decision
Respond to underwriting questions and review the complete written merchant terms before acceptance.
Configure and test
Enable Paya in CMS Max with the approved terminal and matching environment, then exercise success and failure cases.
Accept production
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 form is hosted on Maxforms; the resulting payment relationship and underwriting are provider-controlled.
- Applicant
- Authorized merchant representative who can provide accurate business and ownership information.
- Provider
- Paya or Nuvei controls underwriting, account terms, credentials, terminal services, processing, and settlement.
- CMS Max
- Controls the native application integration, tenant settings, payment context, and supported operational actions.
- Merchant
- Owns account security, policies, customer communication, returns, disputes, reconciliation, and compliance obligations.
- Launch evidence
- Approved account, correct environment, representative tests, live transaction, settlement, and owner sign-off.
Current references
Use live product and provider evidence.
Interfaces, policies, plans, services, pricing, and requirements can change. Verify the current CMS Max configuration and official provider sources during implementation.
Apply for Paya ACH FAQ
Resolve the practical questions before launch.
Turn each answer into configuration, representative testing, monitoring, ownership, and a documented recovery path.
Does submitting the form guarantee approval?
No. Paya or Nuvei evaluates the merchant application and controls the approval decision and account terms.
Is Paya native to CMS Max?
Yes. The current CMS Max application includes a native Paya ACH and bank-transfer provider.
Is Paya the CMS Max card gateway?
The current architecture uses Paya for ACH. Card processing is configured separately through an eligible card provider.
What information should be prepared?
Expect accurate legal business, ownership, bank, website, product, volume, fulfillment, refund, and contact information, subject to the current application.
When can production payments begin?
After provider approval, correct CMS Max configuration, sandbox or controlled testing, operational acceptance, and production activation.
Build for real operations
Start the merchant application with the right owners present.
Use the secure hosted form, then connect approval, configuration, testing, settlement, and support into one launch plan.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.