Preserve the historical fact
The original announcement identified online ordering, digital agency or web development, e-invoicing, and ecommerce enablement categories.
CMS Max and Heartland: A Trusted Partner Retrospective
Company and payment history
Partnership recognition matters most when it becomes accountable implementation.
In 2018, CMS Max announced recognition across four categories in Heartland's then-current Trusted Partner program. This retrospective preserves that milestone without presenting a dated program label as a current certification.
- Dated recognition
- Current provider review
- Merchant-owned account
- Production acceptance
Decision frame
Keep recognition, implementation, and merchant operations distinct.
A partner relationship can improve coordination, but it does not replace merchant underwriting, current product eligibility, technical acceptance, PCI responsibilities, settlement review, disputes, or support ownership.
Verify the current program
Heartland now publishes current developer, software partner, referral partner, API, sandbox, testing, and certification paths on its own website.
Accept the merchant workflow
The final checkout must be approved, configured, tested, monitored, reconciled, and supported for the specific merchant account.
Platform and operating capability
CMS Max connects the website experience to eligible payment providers.
The exact gateway and processing path depends on the merchant, tender, geography, account, integration, and current CMS Max support.
Owned checkout
Keep products, cart, customer context, policies, order records, and support journeys in the CMS Max website experience.
Provider configuration
Connect only an approved merchant-owned account and protect credentials, keys, terminals, and environment settings.
Tokenized flows
Use provider-hosted or tokenized patterns where supported to reduce unnecessary payment-data exposure.
Transaction context
Record provider references and outcomes with the relevant order or payment-form operation.
Refund operations
Exercise eligible void, refund, partial refund, settlement, and reconciliation paths before launch.
Shared support
Separate CMS Max application support, provider account support, merchant operations, customer communication, and accounting ownership.
Implementation workflow
Turn a payment relationship into an accepted production path.
Provider account approval is one milestone inside the complete customer and merchant operation.
- 01
Discover
Confirm tender types, markets, order values, products, subscriptions, forms, refund policy, risk, reporting, accounting, and owners.
- 02
Approve
Complete merchant underwriting and review the provider agreement, pricing, funding, reserves, limits, disputes, termination, and support terms.
- 03
Configure
Use the eligible CMS Max provider path with protected credentials and clearly separated test and production environments.
- 04
Accept
Test approved, declined, interrupted, duplicate, refund, settlement, reconciliation, mobile, accessibility, and support scenarios.
- 05
Operate
Review transaction records, deposits, fees, disputes, failures, account notices, credentials, and incident response.
Practical reference
Use current provider evidence for current decisions.
A historical award or partner label should never substitute for the live merchant agreement or integration documentation.
- Historical milestone
- CMS Max announcement dated October 25, 2018.
- Current provider
- Heartland, a Global Payments company.
- Current program evidence
- Heartland developer and integrated partner pages.
- Merchant ownership
- Provider account, terms, settlement, disputes, and operating decisions.
- CMS Max ownership
- Website experience, supported integration, order or form context, and application operations.
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 the four-category label a current certification claim?
No. This article preserves CMS Max's 2018 announcement as history. Verify current Heartland program status directly with Heartland.
Does a partnership approve a merchant account?
No. The provider controls underwriting, account terms, activation, settlement, disputes, and provider-side support.
Can CMS Max support online payment experiences?
Yes. CMS Max supports eligible checkout and payment-form workflows through configured payment providers.
Who owns PCI compliance?
Compliance is shared across the merchant, CMS Max implementation, payment provider, hosting, staff, policy, and any system that stores, processes, or transmits payment data.
What should be tested before launch?
Test every approved tender and outcome, order or form state, refund path, settlement, reporting, accessibility, mobile use, and support procedure.
Choose the payment path that fits the merchant operation now.
Bring the current provider account, tender requirements, checkout or form workflow, settlement process, risk model, refund policy, reporting, and support owners.