Connectivity & Flows
See what runs on the terminal and what your integration sends to kepa.
All shipped HTTP operations use https://api.kepapay.co. There is no live local terminal HTTP server and no WebSocket session endpoint. Pages marked planned describe target state, not callable behavior.
Live card-present path
1. Collect the card. The Android terminal handles tap, insert, prompts, and PIN.
2. Request authorization. The terminal sends the amount and encrypted payment data to kepa.
3. Finish the card interaction. For contact chip, the terminal gives the bank’s response back to the card.
4. Store the payment ID. Use it for receipts, refunds, reporting, and support.
Offline and deferred authorization
An offline payment is approved by the card and terminal while there is no connection. Deferred authorization is the later request sent when connectivity returns. Treat them as two steps of one payment, not two sales.
If an online outcome is uncertain, query recovery status and reverse the original authorization when required. Do not create a second sale with a new idempotency key merely because the network response was lost.