Skip to main content
The Xendit Terminal APIs power in-person payments across two integration models. Use this overview to identify the right API track before diving into the detailed references.
Terminal API (H2H) is the recommended starting point for most merchants because it provides managed device orchestration, standardized workflows, and the fastest route to certification.

​
Integration options

The Terminal API is the Host-to-Host (H2H) HTTP API. Your backend calls Xendit’s cloud endpoints to create payment sessions, manage terminals, and receive callbacks.

  • Always HTTP — your backend makes REST calls to POST /v1/terminal/sessions and related endpoints.
  • Unified session and callback model that automatically handles retries and reconciliation.
  • BRI/NTT terminals require the Gateway App or H2H SDK for device connectivity. Other providers connect directly.
Begin with the Terminal API (H2H) introduction and follow the Quick Start to stand up sandbox payments in under 10 minutes.

​
Architecture comparison

CapabilityTerminal API (H2H)Terminal C2C API / Terminal C2C SDK
API interfaceAlways HTTP REST via Xendit cloudHTTP REST (C2C API) or native SDK methods (C2C SDK)
Device managementGateway App or H2H SDK handles pairingYour app or service maintains device connections
Session orchestrationManaged by Xendit with standardized callbacksFully custom — implement your own workflows
BRI/NTT pre-installGateway App or H2H SDKGateway App (for C2C API) or C2C SDK (for native)
Other providersNo pre-install neededNo pre-install needed; C2C SDK optional
Time-to-marketFast — fewer edge cases and pre-built flowsLonger — requires bespoke command handling
Recommended forAssisted checkout, staff POS, rapid pilotsKiosks, unattended terminals, advanced custom flows

​
Sample use cases

A national retail chain wants a consistent checkout experience across dozens of staffed stores. Payments need to keep flowing even when teams rotate or terminals move between counters.

H2H excels when you need a managed operations layer that keeps terminals paired, orchestrates retries, and standardizes receipts so every store follows the same playbook.
  • Central operations teams can monitor every device from a single dashboard instead of logging into individual terminals.
  • Regional expansion is simply a matter of adding more terminals; the API contract and callbacks stay identical.