Skip to content
CMS Max Documentation

Payment Gateways

Accept credit card, ACH and PayPal payments through multiple gateway options

Overview

The Payment Gateways plugin provides a unified payment processing solution for your website. It supports multiple credit card gateways (Authorize.net, CardPointe, and Stripe) and ACH bank payments via Paya, and it lets shoppers pay with PayPal once you connect your PayPal Business account. You can also define manual payment methods such as bank transfer or cash on delivery. Only one credit card gateway can be active at a time, but you can enable ACH alongside it.

Setup

  1. Navigate to Settings > Plugins
  2. Find Payment Gateways and click to open the settings page
  3. Click Save and Install
  4. Set up the payment methods you need: enable and configure each gateway, or connect PayPal to offer it at checkout

Configuration

General Settings

Payment Gateways plugin settings

Setting Description
Sandbox Mode When enabled, all gateways operate in test mode. Use this for development and testing before going live.

Merchant Processing (Credit Cards)

Toggle Enable Credit Card Gateway and select one of the available gateways:

Authorize.net

Field Description
API Login ID Your Authorize.net API Login ID
Transaction Key Your Authorize.net Transaction Key
Signature Key Optional. Lets orders held by Authorize.net's fraud filters update in CMS Max as soon as you approve or decline them in Authorize.net. Without it, held orders still update within a few minutes.

To retrieve your API credentials:

  1. Log in at account.authorize.net
  2. From the main menu, select Account > Settings
  3. Click API Credentials & Keys
  4. Copy your API Login ID and paste it into the corresponding field in CMS Max
  5. Click Submit to generate a new Transaction Key, then copy it into CMS Max
  6. Optionally, generate a Signature Key on the same page and copy it into CMS Max. After you save, CMS Max sets up the Authorize.net webhook for you, so held-for-review orders update the moment you approve or decline them

Testing your connection: Enter your credentials, then click Test Connection beneath the Authorize.net fields. The check runs entirely on the server against the values currently shown in the form, including unsaved edits, and never creates a transaction, authorization, or charge of any kind — no card details are involved. The result tells you:

  • Whether your API Login ID and Transaction Key successfully authenticated with Authorize.net
  • Which environment was tested (Production, or Sandbox when Sandbox Mode is enabled)
  • Whether a Signature Key was provided — this part of the test cannot verify the key; the webhook check below does

The test does not save your changes. After a successful test, click Save Changes or Save and Install to persist the values.

Testing the webhook: Once your credentials pass, Test Connection also tests the Authorize.net webhook, which delivers updates such as fraud-review decisions for your orders. The result appears in the same message, separate from the credentials result. Your credentials can be fine while the webhook needs attention.

  • What it checks: that the webhook is registered and active on your Authorize.net account, that it is subscribed to the right events, and that Authorize.net's signed test delivery is accepted with your saved Signature Key. It does this by briefly adding and removing a temporary, inactive test webhook on your account. It does not touch your real webhook and creates no orders.
  • Passed: the message shows "Webhook: passed" and the green success notice. If the temporary test webhook could not be removed from your account, the message adds a note and it is still a pass; the next test removes it.
  • Not set up: the Signature Key is optional. If none is saved, the webhook test is skipped and the green notice shows "Webhook: not set up (no Signature Key saved, optional)". Without the key, fraud-review decisions are picked up by a periodic check within a few minutes instead.
  • Needs attention: the notice turns yellow and lists each problem with what to do next, for example:
    • No Signature Key is saved — add it (Authorize.net > Account > Settings > API Credentials & Keys) and save.
    • The webhook is not registered — save the settings to register it.
    • The webhook is inactive — Authorize.net turns it off after repeated failed deliveries; reactivate it in Authorize.net > Account > Webhooks, or save the settings.
    • The Signature Key does not match Authorize.net — generate a new Signature Key in Authorize.net, paste it here, save, and test again.
    • Authorize.net rejected the webhook test — Authorize.net's own message is shown, with a reference you can give to support.
  • Not tested: if the credentials check fails, or you have unsaved Authorize.net changes, the webhook is not tested (the webhook test uses your saved settings, so save first and test again). If the webhook test is not available for your site yet, the green notice says so and there is nothing to do. If another test is already running, or the checkout service is slow or unreachable, the message says so; try again in a couple of minutes. At most 3 webhook tests run per minute.

Saving: While Authorize.net is the enabled credit card gateway, every Save Changes checks the API Login ID and Transaction Key with Authorize.net first, in Sandbox or Production to match Sandbox Mode.

  • New credentials Authorize.net rejects: nothing is saved. The message "Your Authorize.Net credentials seem wrong. Please use Test Connection and try again." appears in the top right corner.
  • Unchanged credentials Authorize.net rejects: your other changes are still saved, and the same message appears so you know card payments won't work yet.
  • Authorize.net can't be reached or gives an unexpected answer: the settings are saved, and a warning asks you to run Test Connection again later.

If a Signature Key is saved but the webhook could not be registered, you see "Payment gateway settings saved, but the Authorize.net webhook is not registered" instead of "saved and synced". Until it is registered, fraud-review decisions for your orders arrive a few minutes late, through a periodic check. Check the Signature Key, then use Test Connection to see the exact reason. Without a Signature Key there is nothing to register, so no warning appears.

When Authorize.net rejects your saved credentials: this can happen because the account or API user has been deactivated, for example.

  • Customers: they can't pay by card. The payment form shows "Payment gateway configuration error. Please contact support." instead of accepting the card. If Authorize.net refuses the keys only when the customer clicks Submit, the form shows "Card payments are unavailable right now. Please contact us to complete your payment."
  • Payment Gateways page: a red notice directly above the API Login ID field reads "Your Authorize.Net credentials seem wrong. Please use Test Connection and try again." A second line shows Authorize.net's reason and when it happened. The notice appears when a payment form, a save, or a Test Connection of your saved credentials is refused. It stays for up to 14 days, and each new refusal restarts that period.
  • Dashboard: while Authorize.net is your enabled credit card gateway, a red notice at the top of the Dashboard reads "Your Authorize.Net credentials seem wrong, so customers may not be able to pay by card." with Authorize.net's reason and when it happened. It can't be ignored, including from Settings > Dashboard Notifications. Fix It opens the Payment Gateways page. It clears at the same time as the Payment Gateways notice.
  • To fix it: reactivate the account or API user in Authorize.net, or enter new credentials. Then click Test Connection to confirm and save.
  • When the notice clears: right away when Test Connection accepts your saved credentials or a save is accepted, when a payment form next loads successfully, or when you save different credentials. Testing new credentials you haven't saved yet doesn't clear it.

Fraud Detection Suite: Authorize.net includes tools to prevent spam and fraudulent transactions. We recommend enabling these filters in your Authorize.net account:

Filter Recommended Setting
Hourly Velocity Filter 50 transactions per hour, decline
Transaction IP Velocity Filter 3 transactions per hour, decline
Enhanced AVS Handling Filter Decline N & A responses
Enhanced CCV Handling Filter Decline N responses
Regional IP Address Filter Decline all regions except North America

Voids and refunds: to reverse a payment from an order or a form submission, CMS Max offers Void while Authorize.net hasn't settled the charge yet, and Refund once it has. It asks Authorize.net for the charge's current status, so this is right whatever Transaction Cut-Off Time your account uses. That needs the Transaction Details API turned on (see Enabling the Transaction Details API). Without it, CMS Max assumes Authorize.net's default 4:00 PM Pacific cut-off, so if you changed yours it can offer the action Authorize.net then refuses. Nothing is reversed in that case: try again later, or reverse the charge in Authorize.net. A void always cancels the full amount: to give back part of a charge that hasn't settled, wait until it settles and refund that part.

What form payments look like in Authorize.net: when a visitor pays through one of your forms, the charge arrives in Authorize.net with these details filled in:

  • Invoice Number — a short reference in the format F<form id>-<code>, where the code is eight characters (for example F12-3FA9C01B). It groups a form's charges, appears on the submission in your admin (shown as Invoice Number, next to the Transaction ID), and is searchable in your Submissions list. Payments of the same amount made from the same browser session share one invoice number, so use the Transaction ID to match a charge to a single submission. Submitting the same payment again within about two minutes (a double-click, or a retry after a lost page) reuses the same number, so Authorize.net rejects the repeat instead of charging twice.
  • Description — the name of the form the payment came from.
  • Customer email — the payer's email address, when the form collected one.

If you have Email transaction receipt to customer turned on in your Authorize.net account (Account > Transaction Format Settings), Authorize.net will email its own receipt to the payer at that address.

Granting CMS Max access to your account: If you need the CMS Max team to help configure your gateway, you can add them as a user in Authorize.net under Account > User Administration. Create a new user with the role "Account Admin" and the email info@cmsmax.com.

Transaction Audit: Once Authorize.net is your active gateway, a Transactions button appears at the top of this page, giving you a live, searchable copy of your Authorize.net transaction history with printable receipts and CSV export. See Authorize.Net Transaction Audit.

CardPointe

Field Description
Username Your CardPointe gateway username
Password Your CardPointe gateway password
Merchant ID Your CardPointe merchant identifier
Hold Payment When enabled, payments are authorized but not captured immediately. Use this if you need to adjust the captured amount (e.g. for tip adjustments). Your merchant account must be entitled for this capability.

Testing your connection: Enter your credentials, then click Test Connection beneath the CardPointe fields. The check runs entirely on the server against the values currently shown in the form, including unsaved edits, and never creates a transaction, authorization, or charge of any kind — no card details are involved. The result tells you:

  • Whether your Username and Password successfully authenticated with CardPointe
  • Whether the Merchant ID is recognized on CardPointe's site, and whether that merchant account is currently enabled
  • Which environment was tested — Production, or Sandbox when Sandbox Mode is on

Saving: When CardPointe is the selected gateway, Save Changes runs the same check first. If CardPointe rejects the Username and Password, or does not recognize the Merchant ID, nothing is saved and an error message appears in the top right corner. If CardPointe can't be reached or gives an unexpected response, the settings are still saved and a warning asks you to run Test Connection again later. You also get a warning if CardPointe reports the merchant account as disabled. Saving without changing the CardPointe credentials skips the check.

Merchant Security Settings: Below the CardPointe fields, a read-only status shows whether CVV validation and AVS validation are enabled on your CardPointe merchant account — these control whether CardPointe declines a transaction when the card issuer reports a CVV or address mismatch. They do not catch a ZIP code the issuer cannot verify at all (for example a Canadian postal code typed into a US billing ZIP), so payment forms check the format of the billing ZIP before the card is charged. Click Check Security Status to refresh the status using the credentials entered above. These settings cannot be changed from CMS Max (CardPointe provides no way to change them remotely): to turn them on or off, log into the CardPointe web app and go to Administration → Security.

Stripe

When no Stripe account is connected, the Stripe section offers up to two choices. Each choice only appears when it is available for your site:

  • Connect Stripe v2 (under "Connect to Stripe"): one combined card rate and no monthly fee. You set it up on this site in a few minutes and manage payouts in a Stripe Express dashboard. If your site used this connection before and was disconnected, the button reads Reconnect Stripe v2 and restores the same account.
  • Connect to old v1 Stripe (under "Old v1 Stripe"): sign in to a Stripe account you already have. Stripe bills you at your account's rate, CMS Max adds no fee, and you keep your full Stripe dashboard. This choice appears only on sites that CMS Max support has enabled it for. On a site that has used Stripe v2, support first closes any checkout payments still open on Stripe v2, the site then confirms the switch, and payments taken through Stripe v2 are refunded from the Stripe v2 dashboard or by CMS Max support, not from this site.

If neither choice is shown, the section says Stripe payments can't be set up right now. Contact support. After you pick Connect to old v1 Stripe, follow the on-screen sign-in with Stripe. When you return from Stripe, the connected account is saved as your credit card gateway. If another credit card gateway is already taking payments, it stays active and a notice asks you to click Save Changes to switch to Stripe.

If you disconnect and connect through the other choice, payments made through the earlier connection can only be refunded or voided from that Stripe account's dashboard.

Once connected, the Stripe section shows what you pay. An account connected through Connect Stripe v2 shows your current card processing rate for your plan, and if a rate change is scheduled, a second line tells you the new rate and the date it takes effect. After your plan changes, the new plan and its rate show the next time you open this page; if you just changed it, wait about a minute and reload. An account connected through Connect to old v1 Stripe is billed by Stripe directly at your Stripe account's rate, and CMS Max adds no fee.

Connect Stripe v2: where this option is available, click it to start a guided setup that walks you through connecting Stripe without leaving your site. Stripe collects your business and banking details in the same window. If you close the window before finishing, click Continue setup to pick up where you left off, or Cancel setup to remove the pending connection and start over.

Once setup is complete, Open Stripe dashboard takes you to your Stripe dashboard for payouts, disputes, and tax documents, and Manage Stripe account lets you update your business details without leaving your site. When Stripe needs something from you, a notice appears in the Stripe section.

Payment methods: click this to turn individual payment methods on or off, such as Apple Pay, Google Pay, or buy-now-pay-later options. A method you turn on only shows at checkout when Stripe also finds it eligible for the shopper's country, currency, and amount. Affirm and Klarna need a shipping address at checkout to appear as options.

PayPal

The PayPal section links your PayPal Business account to CMS Max so shoppers can pay with PayPal at checkout. The money goes straight to your PayPal account, less CMS Max's fee when your plan has one. The section appears on this page when PayPal is available for your site.

When you offer PayPal, checkout lists PayPal right after the credit card option. A shopper who picks it finishes paying in a PayPal window, using PayPal, Pay Later or Venmo. PayPal decides which of these a shopper can use. Venmo is available only to eligible shoppers in the United States.

If you also turned on PayPal in your Stripe dashboard, Stripe's PayPal option is hidden while you offer PayPal here, so shoppers see one PayPal option. Turn off Offer PayPal at checkout to show Stripe's PayPal instead.

Important: PayPal is not offered when a gift card pays only part of the order. A gift card that covers the whole order works as usual.

Connecting PayPal

  1. In the PayPal section, click Connect PayPal. CMS Max sends you to PayPal.
  2. Log in to your PayPal Business account, or create one.
  3. Confirm your email address with PayPal if PayPal asks you to.
  4. Review the permissions CMS Max asks for, such as taking payments, issuing refunds, and reading your account details and disputes, then agree.
  5. Finish PayPal's steps. PayPal sends you back to the Payment Gateways page.

When PayPal reports your account as ready, the section shows Connected, a Live or Test badge, and your PayPal merchant ID. Live is a real PayPal account. Test is a PayPal sandbox account.

When setup is in progress

If you start PayPal's signup and leave before finishing, or PayPal still needs something, the section shows PayPal setup in progress and lists what is missing. Fix each item in PayPal, then reload the page to check again.

Message What to do
Finish signing up with PayPal, then come back to this page. PayPal has no account for you yet. Click Continue setup, finish PayPal's signup, then come back to this page.
Confirm your email address with PayPal. Open the confirmation email from PayPal and confirm your address.
PayPal cannot accept payments for this account yet. Log in to PayPal to see what it needs. Log in to PayPal and complete whatever it asks for.
CMS Max does not have the permissions it needs. Disconnect and connect PayPal again. Click Cancel setup, then Connect PayPal, and agree to every permission PayPal lists.

While setup is in progress:

  • Continue setup sends you back to PayPal to pick up where you left off.
  • Cancel setup removes the pending setup so you can start over.

If you leave PayPal's signup before finishing, the section stays on PayPal setup in progress until you continue or cancel. PayPal tells CMS Max when you finish, so a setup you finish in PayPal later is picked up without you returning to this page. For 30 days after you start, CMS Max also checks your PayPal account about once an hour, in case that message does not arrive.

If PayPal reports an issue on an account that is already Connected, the issue is listed under the merchant ID. Fix it in PayPal, or click Disconnect and connect again.

Other messages

Message What it means
PayPal setup is not available yet PayPal setup is not turned on for your site. Contact CMS Max support.
PayPal connection status is unavailable right now. Try again in a moment. CMS Max could not reach its payment service. Reload the page in a moment.
Status may be out of date. PayPal did not answer in time, so CMS Max shows the last status it saved. Click Check again.

Offering PayPal at checkout

Once your account shows Connected, the PayPal section also shows the Offer PayPal at checkout toggle.

  • CMS Max turns the toggle on when your account becomes connected. It turns the toggle off when you disconnect, and also when CMS Max finds the account is no longer connected, for example after a disconnect made outside this page.
  • Turn it off to stay connected without offering PayPal to shoppers, then click Save Changes.
  • PayPal counts toward the rule that at least one payment method must be enabled only while the toggle is on and your account is connected.

CMS Max's fee on PayPal payments

When your plan has a CMS Max fee on PayPal payments, the PayPal section shows it under your merchant ID, for example CMS Max fee on PayPal payments: 1.00% + $0.10 (Pro, schedule v2). The fee is a percentage of each payment plus a fixed amount, and it never exceeds the payment. PayPal takes it from each payment when the payment is captured and passes it to CMS Max. The shopper's total does not change.

PayPal's own fees come out of the same payment, as they do for any PayPal payment. You receive the payment minus both fees. For example, on a $40.00 payment with a $1.50 CMS Max fee and a $1.53 PayPal fee, $36.97 reaches your PayPal account.

When CMS Max has scheduled a change, the widget shows the date and what changes. Below your current fee it reads From Dec 1, 2026: 1.20% + $0.10 for a new rate, or From Dec 1, 2026: no CMS Max fee on PayPal payments when the fee ends. When your plan has no fee yet, a single line reads CMS Max fee on PayPal payments from Dec 1, 2026: 1.20% + $0.10. Fee increases are announced at least 30 days ahead.

Nothing shows when neither your plan today nor a scheduled change has a CMS Max fee on PayPal payments, or when CMS Max cannot load its rates right now.

Orders paid with PayPal

An order paid with PayPal shows PayPal as its payment method, or PayPal (Venmo) or PayPal (Pay Later) when the shopper used one of those. Its Transaction ID is the ID PayPal gives the payment. See Managing Orders for the PayPal order statuses and refunds.

  • Paid right away: most PayPal payments are paid when the order is placed.
  • Held for review: PayPal sometimes holds a payment for review. The order arrives with payment status Pending and order status On Hold, and the shopper is told PayPal is reviewing the payment. PayPal tells CMS Max as soon as it decides, and CMS Max also checks with PayPal about once an hour for 30 days, in case that message does not arrive. When PayPal clears the payment, the order becomes Paid and moves to Processing, and the shopper is emailed. When PayPal declines it, the order becomes Failed. If PayPal still holds the payment after 30 days, CMS Max stops checking by itself, but the order still updates when PayPal reports its decision. Until then it stays On Hold. Check the payment in your PayPal account and update the order yourself, or contact support.
  • Refunds: you refund a PayPal payment in full or in part from the order page. PayPal returns CMS Max's fee in proportion to the amount you refund, so a full refund returns the whole fee. PayPal's own fees follow PayPal's refund rules. PayPal payments cannot be voided. PayPal allows refunds for 180 days after the payment.
  • Refunds made in PayPal: a refund you make in your PayPal account instead of CMS Max appears on the order about five minutes later, in the order's refund history. The order's payment status changes the way it does for a refund made in CMS Max.
  • Cases: when a buyer opens a case against a PayPal payment, you answer it in PayPal's Resolution Center. CMS Max cannot answer, accept or escalate a case. The order page shows the case, what PayPal allows for a refund while it is open, and a link to the Resolution Center. See Managing Orders for the details.

Disconnecting PayPal

  1. In the PayPal section, click Disconnect.
  2. Confirm in the dialog.

CMS Max stops offering PayPal at checkout and stops using your PayPal account for new payments. The permissions you granted stay in PayPal until you remove them, so the section reads "PayPal was disconnected. Remove CMS Max's permissions in your PayPal account if you no longer use it." To remove them, log in to PayPal, open your account settings, find the apps and services with access to your account, and remove CMS Max. You can click Connect PayPal again at any time.

If you remove CMS Max's permissions in PayPal yourself, PayPal tells CMS Max and the PayPal section disconnects on its own. It reads "PayPal reports that this PayPal account removed CMS Max's permissions. Connect PayPal again to take PayPal payments." Shoppers stop seeing PayPal at checkout, and the Offer PayPal at checkout toggle turns off the next time you open the Payment Gateways page. Click Connect PayPal to agree to the permissions again.

You can still refund earlier PayPal orders after you disconnect, as long as PayPal still lets CMS Max refund them. Once you remove CMS Max's permissions in PayPal, the order page shows "CMS Max no longer has permission to refund this PayPal payment. Refund it from your PayPal account."

ACH Payments (Paya)

Toggle Enable ACH Payments to accept bank transfers via Paya. ACH transactions typically settle within 2–5 business days.

Field Description
Paya Gateway Terminal ID The terminal ID provided by Paya for ACH processing

Automatic status sync: Because ACH takes days to settle, orders and form payments start out Pending. A background job checks Nuvei/Paya's settlement reports twice a day and automatically moves each transaction to Paid/Settled (cleared) or Failed (returned by the bank, with the return code recorded) — no manual reconciliation needed. See the Failed ACH panel on the eCommerce dashboard for anything that came back returned. ACH orders remain On Hold and are not sent to DoorDash or ShipStation until the payment clears. If the order is cancelled before settlement, a later settlement updates its payment record but does not release fulfillment.

Applying for a Paya account: To get started with Paya, you will need to provide:

  • Business legal name, Tax ID (EIN), and website URL
  • Business address and phone number
  • Contact person details (name, phone, email)
  • Owner information (name, email, phone, ownership percentage — must be 25%+)
  • Transaction estimates (average amount, max per transaction, monthly volume)
  • Documentation: voided check or bank letter, one month's bank statement, and a current processing statement or business license

Contact CMS Max support for assistance with the Paya application process.

Manual Payment Methods

Manual payment methods

Below the online gateways, you can add custom offline payment methods (e.g. Bank Transfer, Money Order, Cash on Delivery). Orders placed with a manual method will have a "pending" payment status until you mark them as paid in the admin panel.

For each manual method, provide:

Field Description
Name The method name shown at checkout (e.g. "Bank Transfer")
Additional Details A short description shown below the method name
Payment Instructions Instructions shown to the customer at checkout and on the order confirmation
Active Toggle the method on or off without deleting it

Manual methods can be reordered by dragging them in the list.