Reconcile a created/processing row via DOKU transactions-status
Authorization
cookieAuth JWT access token set by /auth/google/callback or /auth/refresh
In: cookie
Path Parameters
Response Body
application/json
application/json
application/json
curl -X POST "https://example.com/fiat/deposits/string/sync"{ "id": "string", "kind": "string", "providerRef": "string", "providerStatus": "created", "grossIdr": "string", "feeIdr": "string", "netIdr": "string", "paymentUrl": "string", "feeStatus": "string", "currency": "IDR", "createdAt": "2019-08-24T14:15:22Z"}Create a Checkout deposit intent (DOKU-hosted page, all channels) POST
netAmountIdr is the NET credited to the user (minimum Rp100.000, API-enforced — no DOKU minimum). Global PeridotID fee = 0.1% of net, min Rp100, no cap; when `clientId` is given the app's topup fee stacks on top. gross = net + fee, quoted upfront and snapshotted on the row. DOKU charges its own provider fee separately. The page is routed to the caller's sub-account. The customer is charged gross; fiat settles 100% to the user IDR account as points backing. On verified payment the backend issues NET points (user) + FEE points (Treasury) on the Unified Ledger — the Saldo is usable in seconds without waiting for fiat settlement. The API never debits a fee after settlement.
Cancel a created internal-credit intent POST
Next Page