Payment
terminalSerial: you address the device by IP.Beta — Early Access
Pick a variant first
| Sync | Async | |
|---|---|---|
| Prefix | /sync/ | /async/ |
| HTTP response | The full transaction result | A TERMINAL_ACKNOWLEDGED acknowledgement |
| Blocks? | Yes, until the acquirer answers | No |
| Outcome arrives | In the response | On your events_webhook_url |
| Operations | 10 | 7 |
Request shape
{
"amount": {
"subtotal_iva0": 10000,
"subtotal_iva": 0,
"iva": 0
},
"client_transaction_id": "c5a3f3be-9d6f-4d39-8af5-58dbb589af79"
}| Element | Rule |
|---|---|
amount | Integers only. CLP has no decimals — 10000 is 10.000 CLP |
client_transaction_id | UUID v4. It is your idempotency key — reuse it on retries |
transaction_reference | Required on capture, re-authorization, void and refund. Comes from rawResponse.transaction_reference of the original operation |
currency field — the terminal's DMS configuration decides it.IVA
explicitly — the terminal does not compute it for you:
| Field | What goes in it |
|---|---|
subtotal_iva | Net amount subject to IVA |
subtotal_iva0 | Amount exempt from IVA |
iva | The IVA itself: subtotal_iva × 0.19 |
"amount": { "subtotal_iva": 10000, "iva": 1900, "subtotal_iva0": 0 }whole amount in
subtotal_iva0 and leaves the other two at 0. Either way the three fields arerequired.
Tips and cashback
| Endpoint | Tip | Cashback |
|---|---|---|
/sync/charge, /sync/authorization | Collected on the terminal screen when enabled in DMS | Not accepted |
/sync/pos_tip | amount.tip | cashback_amount |
/async/charge | amount.tip | cashback_amount |
/async/pos_tip | amount.tip | cashback_amount |
200 does not prove the tip was applied. Confirm against the amounts in the response or the final APPROVAL event.Folders
Got a suggestion on this documentation? Contact us.
Modified at 2026-09-02 01:08:15