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
Terminal API (H2H)
Terminal API (C2C)
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.
Client-to-Client (C2C) gives you direct control over commands sent to terminals. You can interface with terminals in two ways:
- Terminal C2C API (HTTP) — Send REST commands (
POST /commands/pay, etc.) over the local network. BRI/NTT require the Gateway App; other providers work directly. - Terminal C2C SDK (native) — Call Android/iOS SDK methods directly. For BRI/NTT the SDK is the required install; for other providers it is an optional convenience.
- Ideal for kiosks, offline-first workflows, and custom hardware setups.
- Requires custom handling of device states, receipt delivery, and failure recovery.
Choose C2C only if you have strong device engineering capabilities — mixing H2H and C2C within the same deployment is unsupported.
Architecture comparison
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.
An experiential marketing team is rolling out unattended kiosks in malls and airports. Each kiosk needs local-device logic and the ability to continue operating if connectivity blips.
C2C offers direct terminal control so your kiosk software can decide exactly when to prompt, cancel, or retry while still working with your chosen hardware.
- Fallback plans—like queueing payments until the mall network recovers—are easier to tailor for each venue.
