Connect card payments
Connect your own Authorize.Net, NMI or Helcim account so you can charge cards, keep cards on file, hold copays and let patients pay online.
CliniReady uses your practice’s own card processor account. Money goes straight from the processor to your bank. Card numbers are typed into the processor’s secure card form and never reach CliniReady; only the card brand and last 4 digits are kept.
Once connected, you can charge cards at checkout and on accounts, keep cards on file, run memberships, hold copays before visits, put holds on virtual care requests, and let patients pay in the portal.
Before you start
- Have an account with Authorize.Net, NMI or Helcim, and its API credentials.
- Only owners and admins can connect or change the account. Billing staff can see which account is connected; for them the page says Only the practice’s owners and admins connect or change this account.
- You need a fresh sign-in (within about the last 10 minutes; unlocking with your PIN doesn’t count). If not, you’ll see For your security, sign out and sign back in, then make this change. Sign in again and come straight back.
How to connect
- Go to Practice admin › Payments › Card payments.
- Under Gateway, choose Authorize.Net, NMI or Helcim.
- Under Account, choose Sandbox (test) to try it with test cards, or Live for real payments.
- Enter the credentials for your gateway (see below).
- Click Check and save. CliniReady checks the credentials with your gateway before saving them. When it works, you’ll see Connected. Patients can now pay online.
Authorize.Net
- API Login ID and Transaction Key: in Authorize.Net under Account › API Credentials & Keys.
- Your account also needs a Public Client Key (Account › Security Settings › Manage Public Client Key).
NMI
- Public tokenization key: in NMI under Settings › Security Keys, a key with “Tokenization” permission. It runs the secure card form patients see.
- Private security key: same place, a key with “API” permission.
Helcim
- API token: in Helcim under All Tools › Integrations › API Access Configurations › New API Access. Set Transaction Processing to Admin (for refunds) and General and Settings to Read & Write (to remove saved cards).
- In the same access, tick Checkout integration and add the staff app’s address and your patient portal’s address. The page shows the staff app address to copy. This lets the secure card form open there.
- Sandbox is a Helcim developer test account (ask Helcim for one). Live is your real account.
After you connect
The page shows the gateway, Sandbox (test) or Live, and (for Authorize.Net) the API Login ID. Click Change to switch gateways, accounts or keys.
Secret keys are stored encrypted and never shown again. To change one, enter it again.
Every time the account is connected or changed, each active owner of the practice gets an email saying so, including the owner who made the change. If you didn’t expect one, check this page.
Good to know
- Switching gateways: cards saved with the old gateway can’t be charged through the new one (you’ll see That saved card isn’t on file anymore.). Save the card again, and move any membership to the new card.
- Moving from Sandbox to Live: test cards saved in a sandbox account belong to that account. Remove them and save real cards once you’re live.
- What the processor sees: generic descriptions only, such as “Account payment” or “Membership”, never clinical details.
- In sandbox mode, a membership shows Renew now (test), so you can try a renewal without waiting.
Troubleshooting
| On screen | What it means | What to do |
|---|---|---|
| Authorize.Net didn’t accept these credentials (…). Check the API Login ID, the Transaction Key and Sandbox / Live. | The keys are wrong, or for the other environment. | Copy the keys again and check Account. |
| Authorize.Net has no Public Client Key for this account. … | The account has no public client key yet. | Create one in Authorize.Net, then save again. |
| NMI didn’t accept the private security key (…). Check the key and Sandbox / Live. | The private key is wrong. | Copy it again. |
| Enter the public tokenization key (NMI: Settings › Security Keys, a “Tokenization” key). | The public key is missing or not accepted. | Create or copy the tokenization key. |
| Helcim didn’t accept this API token (…). Check you copied all of it. | The token is incomplete or wrong. | Copy the whole token. |
| Couldn’t reach [gateway]. Please try again. | The gateway didn’t answer. | Try again in a few minutes. |
| Online payments aren’t switched on for this system yet. | Card payments aren’t available on this CliniReady system. | Contact support. |
| The card form didn’t load. Try again. (at checkout) | The secure form couldn’t open. With Helcim, the addresses may be missing from Checkout integration. | Check the Helcim access settings, then try again. |
Related
Still stuck? Contact support and we’ll help. Please don’t include patient information.
Checked against the app on November 14, 2026