reseller

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

Send a deposit back to the card it came from.

Ҳамаи нуқтаҳои ниҳоии reseller

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати reseller.manage бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ҷое, ки рақами мушаххаси ташкилоти шумо ҷойгир аст

Ин нуқтаи поёнӣ org_id-ро ҳамчун параметри дархостӣ қабул мекунад. Онро хориҷ кунед ва даъват тамоми зердарахти иҷораи шуморо фаро мегирад; барои маҳдуд кардани даъват ба як созмон онро фиристед.

Rakami муайянкунандаи ташкилоти шумо дар экрани калидҳои API дар панели идоракунии шумо, дар паҳлӯи худи калид ҷойгир аст. Ин як раками муайянкунанда дар ҳар یک дархосте, ки шумо иҷро мекунед, якхела аст.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

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 '{  }'

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

⛔ **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`.

Параметрҳо

НомНамудТалаб карда мешавадИн чӣ аст
topUpId (path)UuidБале
org_id (query)UuidНеWhich 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…

Ҷисми дархост

НомНамудТалаб карда мешавадИн чӣ аст
amount_minorintegerНеOmit to refund everything still refundable on the deposit.
reasonstringНе

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
quoted_minorintegerНеWhat the customer asked to add, and what the screen promised them.
settled_minorinteger | nullНеWhat actually arrived. **`null` = not known yet**, never zero.
fee_minorinteger | nullНеWhat the provider kept out of the settlement. **`null` = not known**, never zero — recording an unknown as `0` would credit the customer the shortfall.
credited_minorintegerНеWhat went into the balance — `settled_minor - fee_minor`.
shortfall_minorinteger | nullНе`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>Не
is_autobooleanНеWhether a standing instruction created this, rather than a person.
action_urlstringНеWhere 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.
idUuidБалеUUIDv7 identifier — sortable by creation time (docs/02 §8).
amount_minorintegerБале
currencystringБале
statusstring<pending, requires_action, captured, failed>Бале⛔ 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_minorintegerБале
refundable_minorintegerБалеWhat is left to send back to the card. Zero unless it captured.
gatewaystringНеThe provider's driver — `stripe`, `paypal`, `nowpayments`. ⛔ Never a credential and never a merchant-account reference: which account your provider banks with is their commercia…
errorstringНеThe gateway's refusal, in words the customer can act on.
created_atstringБале
captured_atstring | nullНе

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 422 · 429