Documents

Scope: document:read, or any ops scope that creates documents (cards:issue / cards:read / cards:topup / cards:freeze / withdraw / gift:purchase / esim:* / reconciliation:read). Every create that uses ext_id can be polled:

GET https://api.imbawallet.com/partner/documents/{ext_id}
Authorization: Bearer <access_token>

{
  "ext_id": "withdraw-20260710-001",
  "type": "withdrawal",
  "ref_id": "019d0123-bf52-74b5-b78a-76c49333e82d",
  "status": "processing",
  "response": {},
  "created_at": "2026-07-10T09:20:00.000Z",
  "updated_at": "2026-07-10T09:21:15.000Z"
}

HTTP	When
`200`	Document found — read `status` / `response`
`403`	Missing `document:read` and no matching ops scope
`404`	Unknown `ext_id` for this partner (or not created yet)

Document types

`type`	Created by
`withdrawal`	`POST /partner/withdrawals`
`card_issue`	`POST /partner/cards`
`card_topup`	`POST /partner/cards/{card_id}/topups`
`card_freeze`	`POST /partner/cards/{card_id}/freeze`
`esim_purchase`	`POST /partner/esims`
`esim_topup`	`POST /partner/esims/{esim_id}/topups`
`gift_purchase`	`POST /partner/gift-cards`

Document status moves from processing toward terminal values (done / failed / card_issued / … by type). Operation details live in response (for example card_id, business status, error).

How to check status

Polling: call this endpoint until status is terminal (a few seconds between polls; respect rate limits).
Webhook: on terminal ext_doc, IMBA sends *.status_changed (at-least-once; idempotent by event_id). Keep polling as a fallback.
Secrets (PAN/CVV, LPA, gift code) are not required in webhooks or document_get — use the product GET (/cards/{card_id}, /esims/{esim_id}, /gift-cards/{purchase_id}).

Stuck `card_issue`

A card_issue that remains processing with no card / charge progress is closed by IMBA as failed with error=issue_timeout (see Cards). You get a webhook and a terminal document. Funds were not charged. Retry with a new ext_id — the same ext_id replays the stored failed result. Documents are not deleted. Use documents for in-flight work keyed by your ext_id (this is the order / reference lookup). There is no other universal transaction-search path. Card merchant authorizations are not listed here. Product secrets stay on the product GET endpoints (step 3 above).

Get started

Money

Products

Operations

Document types

How to check status

Stuck `card_issue`

​Document types

​How to check status

​Stuck card_issue

Document types

How to check status

Stuck `card_issue`