Processor: Checkout.com
Checkout.com is a V1 payment processor configured at the center level. It supports online card transactions for Zenoti's Webstore and guest portal. Terminals, stored accounts, and recurring-card charges are not supported in the Zenoti integration (see the capabilities table).
Before you begin
Permission: Center-level payment configuration access is required.
Checkout.com merchant-side prerequisites
- Active Checkout.com account via the Checkout.com Hub.
- Per-country / per-currency activation β Checkout.com activates card schemes per country; confirm your target markets are enabled.
- Return URL allow-list β share the Zenoti return domain with Checkout.com so the hosted page can redirect.
Credentials
| Field | Source / owner | What to enter |
|---|---|---|
| Public key | Checkout.com Hub β Keys / API settings | Used client-side to tokenise card data on the hosted page. |
| Secret key | Checkout.com Hub β Keys / API settings | Used server-side by Zenoti to authorise transactions. Treat as sensitive. |
Note: Checkout.com issues separate keys for test (
pk_test_.../sk_test_...) and live (pk_live_.../sk_live_...) environments. Use test keys during verification; switch to live keys only after the test flow succeeds.
Network requirements
| Direction | Port | Protocol | Why |
|---|---|---|---|
| Outbound from Zenoti to Checkout.com API | 443 | HTTPS | Charge, refund, status calls |
| Outbound from guest browser to Checkout.com hosted payment page | 443 | HTTPS | HPP (Hosted Payment Page) card entry |
| Outbound from Checkout.com to Zenoti | 443 | HTTPS | Post-payment callback |
Checkout.com capabilities in Zenoti
| Capability | Supported |
|---|---|
| Online card payments (HPP) | Yes |
| Refund | Yes |
| Void | No (no VoidTransaction in code β use a refund for cancellations) |
| Stored accounts | No (CanProcessorSaveCards = false) |
| Recurring card-on-file | No |
| Terminal (POS (Point of Sale)) | No |
Capability correction (April 2026): All three are incorrect for the Checkout.com V1 integration. If you require those capabilities, choose a different processor.
Configure Checkout.com
- At the center level, navigate to Configuration > Payments > Settings (the center-scope caption of the Payments row).
- Select Checkout.com as the payment processor.
- Enter the Public key and Secret key from the Checkout.com Hub.
- Enable the card payment channel.
- Select Save.
- Select Test to verify β run a small test-mode charge first.
Process a payment
- Guest selects Checkout.com on the Webstore.
- Zenoti redirects to the hosted page.
- Guest completes the card payment.
- Checkout.com redirects back with the result; Zenoti closes the invoice on success.
Process a refund
Refunds use the Secret key configured at setup.
- Open the invoice, select the Checkout.com transaction, choose Refund.
- Confirm β full or partial depending on your workflow. [SOURCE GAP β PM VERIFY: partial and multi-partial refund support in the Zenoti integration.]
Refund β dual-system perspective
| System | What happens |
|---|---|
| Zenoti | Negative payment line on the invoice; Collections shows a refund row tied to the original transaction. |
| Checkout.com | Separate refund record against the original transaction; appears on the Checkout.com dashboard. Match key: Checkout.com transaction ID or Zenoti invoice number. |
Edit or reverse a posted payment
| Invoice state | What you can do |
|---|---|
| Open | Remove the Checkout.com payment line, then refund if a charge has already hit Checkout.com. Void is not available. |
| Closed | Reopen if permissions allow, or post a compensating refund. |
Failure modes
| Failure mode | User-visible symptom | Resolution |
|---|---|---|
| Checkout.com unreachable | HPP fails to load or times out. | Check outbound HTTPS and the Checkout.com status page. Invoice remains open. |
| Authentication / bad secret | Every transaction fails with auth error. | Re-verify test vs live key; re-copy from the Checkout.com Hub. |
| Card declined | HPP shows issuer decline. | Guest retries. |
| Amount out of range | Checkout.com rejects the amount. | Per-country minimums and maximums apply; contact Checkout.com. |
| Currency mismatch | Transaction rejected. | Confirm the center currency is activated for the Checkout.com account. |
| Settlement failure | Transaction approved but missing from settlement. | Raise with Checkout.com using the transaction ID; do not re-charge. |
Settlement and reconciliation
Checkout.com settlement is typically T+2 to T+4 in most markets, processor-side and scheme-dependent. Weekends and bank holidays extend the window. [SOURCE GAP β PM VERIFY: exact T+N per market.]
| Source | Report / view | Match key |
|---|---|---|
| Zenoti | Collections report (filter: Payment Method = Checkout.com) | Checkout.com transaction ID + Zenoti invoice number |
| Checkout.com | Checkout.com Hub β Payments / Reports | Same fields |
Recommended cadence: daily during the first month after go-live; weekly thereafter.
Tips
- Checkout.com is primarily used for online payment flows. For in-store terminal payments, use a processor that supports POS terminals.
- Verify that the account is in live mode (not test mode) before processing real payments.
- Keys rotated on the Checkout.com Hub must be re-entered in Zenoti immediately β otherwise every transaction fails.