Get Operation
Look up the final status of a funding or withdrawal by your idempotency key.
Returns the recorded outcome of a Fund Card or Withdraw from Card request that carried an X-Idempotency-Key. Use it after a network timeout to determine whether the operation was actually processed, before deciding to retry.
Path parameters
idempotencyKeystringpathrequiredThe X-Idempotency-Key you supplied on the funding or withdrawal request.
Response
operationIdstringServer-side operation id (oaop_…), also returned by the original fund/withdraw response.
idempotencyKeystringThe idempotency key you supplied.
typestringFUNDING or WITHDRAWAL.
cardIdstringamountintegerAmount in cents.
statusstringPROCESSING, COMPLETED, or FAILED.
createdAtintegerEpoch milliseconds.
{
"code": 0,
"message": "SUCCESS",
"data": {
"operationId": "oaop_65dc71de43174896ae57",
"idempotencyKey": "topup-2026-07-10-001",
"type": "FUNDING",
"cardId": "cid_1234567890",
"amount": 100000,
"status": "COMPLETED",
"createdAt": 1640995200000
}
}Interpreting the status
status | Meaning | What to do |
|---|---|---|
COMPLETED | The funds moved exactly once. | Nothing — the operation succeeded. Retrying the same key just returns the same result. |
PROCESSING | The request was accepted and is still being applied (or a prior attempt is in flight). | Wait and poll again. Do not submit a new key yet — that risks a double movement. |
FAILED | The operation did not move any funds. | The key is terminal. Fix the cause and submit a new idempotency key to retry. |
A 404 means no operation exists for that key under your project — either the key was never used, or it was sent without an X-Idempotency-Key header (in which case the request was processed without idempotency tracking).