reseller

POST /v1/reseller/client-wallets/top-ups/{topUpId}/refunds

Send a deposit back to the card it came from.

All reseller endpoints

Authentication

Send an API key as a bearer token. The key must carry the reseller.manage permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/reseller/client-wallets/top-ups/{topUpId}/refunds \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

⛔ **Back the way it came.** There is deliberately no "refund to wallet" option: a top-up already *is* wallet credit, so crediting it again would be a no-op wearing the name of a remedy, and wallet credit is an opt-in under consumer law rather than something silence can agree to. The balance is debited first and the gateway refund taken second; if the client has already spent the deposit the refund is refused with 422, and if the gateway declines it the balance is put back. Requires `reseller.manage`.

Parameters

NameTypeRequiredWhat it is
topUpId (path)UuidYes
org_id (query)UuidNoWhich of your organizations this applies to. Required only when you belong to more than one here — otherwise it is inferred, and an id outside your direct memberships is a 404 r…

Request body

NameTypeRequiredWhat it is
amount_minorintegerNoOmit to refund everything still refundable on the deposit.
reasonstringNo

Response

NameTypeRequiredWhat it is
quoted_minorintegerNoWhat the customer asked to add, and what the screen promised them.
settled_minorinteger | nullNoWhat actually arrived. **`null` = not known yet**, never zero.
fee_minorinteger | nullNoWhat the provider kept out of the settlement. **`null` = not known**, never zero — recording an unknown as `0` would credit the customer the shortfall.
credited_minorintegerNoWhat went into the balance — `settled_minor - fee_minor`.
shortfall_minorinteger | nullNo`quoted_minor - credited_minor`. `null` until the top-up settles. Derived rather than stored: it is a difference between two recorded facts, and a stored copy is a second source…
purposestring<general, ai>No
is_autobooleanNoWhether a standing instruction created this, rather than a person.
action_urlstringNoWhere the customer must go to finish paying — a crypto pay-link or an SCA challenge. Losing it strands a pending top-up with no way to complete it.
idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
amount_minorintegerYes
currencystringYes
statusstring<pending, requires_action, captured, failed>Yes⛔ Credit is written on `captured` only. `pending` (a crypto invoice confirming) and `requires_action` (3-D Secure) both mean the money has not arrived yet.
refunded_minorintegerYes
refundable_minorintegerYesWhat is left to send back to the card. Zero unless it captured.
gatewaystringNoThe provider's driver — `stripe`, `paypal`, `nowpayments`. ⛔ Never a credential and never a merchant-account reference: which account your provider banks with is their commercia…
errorstringNoThe gateway's refusal, in words the customer can act on.
created_atstringYes
captured_atstring | nullNo

Errors this endpoint can return

401 · 403 · 404 · 422 · 429