Skip to main content
Welcome to the Terminal SDK hub. Use this page to pick the right SDK pathway and to understand how the host-to-host (H2H) and client-to-client (C2C) options differ.

​
Why build with Terminal SDKs?

  • Single app experience: Keep staff or customers inside your Android or iOS app while you manage payments, receipts, and device states end-to-end.
  • Provider flexibility: Add or swap terminal providers (BRI, Cashup, NTT, and more) without rewriting your integration from scratch.
  • Shared tooling: Rely on the same credential, logging, and monitoring patterns across both SDK families.

​
Choose the right track

The H2H SDK provides device connectivity for the H2H path. Payment API calls are always HTTP via the Terminal API — the SDK handles the device communication layer only.

  • Ideal for staffed environments where associates stay in a single mobile workflow.
  • Leverage standardized payment sessions, callbacks, and reconciliation flows.
  • Required for BRI/NTT terminals on the H2H path if you choose not to use the Gateway App.
Jump to the Terminal H2H introduction to dive into platform concepts and SDK setup.
BRI / NTT pre-install required: On the H2H path, install either the Terminal Gateway App or the Terminal H2H SDK. On the C2C path, install the Gateway App (for Terminal C2C API) or the Terminal C2C SDK (for native method calls). Other providers (Cashup, SHC) connect directly without any pre-install.

​
Implementation checklist

1

Align on operating model

Confirm whether each merchant location will run the managed H2H track, the direct C2C track, or a mix by venue. Document expectations in your rollout plan.
2

Provision credentials

Request the appropriate CLIENT_KEY and API credentials from the Xendit In-Person Payment team, noting that sandbox and production environments use separate keys.
3

Prepare device inventory

Maintain terminal IDs, IP addresses, and provider mappings for every site. This ensures your app can register terminals programmatically.
4

Plan observability

Decide how you will surface command results, device connectivity, and reconciliation status to operations teams before you go live.

​
Next steps

Terminal H2H SDKs

Follow platform-specific guides for Android and iOS implementations.

Terminal C2C SDKs

Explore command APIs, provider helpers, and kiosk deployment patterns.

Gateway App

Compare running SDKs inside your app versus delegating device control to the Gateway App.

Migration guides

Review detailed migration paths for teams updating from legacy SDKs.