Cloud Payment Service release notes
This section contains release notes for the Cloud Payment Service(CPS). Your services use the CPS API to control P6X and Apollo family terminals over the internet, with no local connection to the terminal. We deploy every CPS release ourselves, so you do not need to update anything.
2026 releases
- Version 1.4.1: hotfix that adds the SSL.com TLS root certificates
- Version 1.4.0: a 10-minute webhook timeout, an earlier disconnect webhook for Apollo family terminals,
and
transactionUUIDin the card webhook - Version 1.3.9: no more 02:00 UTC request blocking for Apollo family terminals, and extended card information in the card webhook
- Version 1.3.8: faster terminal reconnection after a service restart
2025 releases
- Version 1.3.7: QR code scanning support, and no more duplicate receipts in a session
- Version 1.3.6: scheduled and offline cancel or commit, session reconciliation, and the Transaction Context request
- Version 1.3.5: a 90-day session archive, and session cleanup when you delete a terminal
2024 releases
- Version 1.3.4: stability fixes for P6X terminals and the state webhook
- Version 1.3.3: a main title for UI messages, and capacity for more terminals
- Version 1.3.2: Apollo Polar support, and a choice of authorization payment types for Apollo family terminals
- Version 1.3.1: Apollo family terminals resume the UI after a restart, and restart a transaction after a card timeout
- Version 1.3.0: pre-authorization updates for Apollo family terminals
- Version 1.2.9: faster connection handling for Apollo family terminals
2023 releases
- Version 1.2.8: support for Apollo family terminals that only run the Host Adapter
- Version 1.2.7: a hidden amount option, automatic voids after 48 hours, and automatic reconnection
- Version 1.2.6: an optional merchant reference on authorize
- Version 1.2.4: zero-amount authorize, and a stop request in every state
- Version 1.2.3: an optional callback for the authorize request
- Version 1.2.2: session filters
How the Cloud Payment Service connects
The Cloud Payment Service sits between your payment terminals and your own services:
The components are:
- Payter Terminal: reads the customer's card, and shows the screens that your services request. It connects to the Cloud Payment Service over the internet.
- Cloud Payment Service: passes requests from your services to the terminal, and reports terminal events, such as a card read or a disconnection, back to your services through webhooks.
- Your services: send requests to the CPS API, such as a request to start, authorize, or commit a payment, and receive the webhook calls.