Terminal Integration Overview

What developers can build on for RevKeen card-present terminals today

RevKeen terminals take card-present payments on PAX devices. Merchants start terminal payments, voids and refunds from the dashboard.

Partner-only. The terminal payment and terminal device endpoints are not part of the public RevKeen API or SDK, and have no public API reference. They are available to approved partners only. Contact support@revkeen.com if you need card-present payments in your own software.

What you can use today

  • Webhooks. Every terminal payment and reversal publishes an event you can subscribe to.
  • Invoices and payments. A terminal payment pays an invoice, so the invoice and payment data you already read through the public API reflect it.
  • Refunds through your gateway. A refund created with the public Refunds API is processed through your card gateway, not on the terminal. See Refunds & Voids.

Terminal webhook events

EventWhen it is sent
terminal_payment.requestedA payment was sent to a terminal
terminal_payment.succeededThe payment was approved
terminal_payment.declinedThe card was declined
terminal_payment.cancelledThe payment was cancelled before completion
terminal_payment.errorThe payment failed, for example a timeout or lost connection
terminal_refund.succeededA refund on the terminal succeeded
terminal_void.succeededA void on the terminal succeeded

Terminal payment events include the payment id, amount, currency, status, device_id and terminal_serial. See the webhook event catalogue for full payloads.

Operating principles

  • Treat webhooks as the source of each terminal result, and process them idempotently.
  • A timeout or lost connection is a normal case. Check the payment before starting another one, because a terminal can complete a payment even when the initiating session did not receive the result.
  • Voids and refunds have different eligibility and money effects. Follow Refunds & Voids.

Next steps

API reference for this workflow

Owner: david · Reviewed 30 Sep 2026 · Next review 30 Oct 2026

On this page