Skip to main content

Overview

After users complete transfers in a widget, you can query operations for reporting, support, and reconciliation. For status meanings and the webhooks that fire as an operation progresses, see Operation lifecycle. Auth: X-API-Key (raas_sandbox_* / raas_live_*).

Status filter values

List operations

Set BASE_URL from the Partner API overview.

Query parameters

Response shape

Get operation detail

Detail responses include funding/payout method summaries, amount breakdown, status timeline, references (pickup PIN as PAYOUT_CODE when issued), documents descriptors, and failure reason when applicable. When the operation selected a catalog payer, payout also includes payerCode (and stateCode / cityCode when the SKU is geo-scoped). Field schemas are in the Partner API overview OpenAPI (Get operation details).
For the cash-pickup PIN, see Payout code (PIN) — pull from this GET or handle operation.references_available. The list endpoint does not include references.
For real-time status updates, subscribe to operation.created, operation.completed, operation.failed, and operation.cancelled — see Webhook events.

Next steps

Payout code (PIN)

Pull or webhook for the pickup PIN.

Operation lifecycle

Statuses and webhook mapping.

Users and CIP

User list, block/unblock, CIP readiness.

API overview

Envelopes, auth, pagination conventions.