reseller

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

Send a deposit back to the card it came from.

Semua titik akhir reseller

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin reseller.manage; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Tempat ID organisasi Anda dimasukkan

Titik akhir ini menerima org_id sebagai parameter kueri. Kosongkan parameter tersebut dan panggilan ini akan mencakup seluruh subpohon penyewa Anda; kirimkan untuk mempersempit panggilan ke satu organisasi.

ID organisasi Anda berada di layar kunci API di dasbor Anda, di sebelah kunci itu sendiri. Itu adalah ID yang sama dalam setiap panggilan yang Anda buat.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

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

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

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

Parameter

NamaJenisWajibTentang apa ini
topUpId (path)UuidYa
org_id (query)UuidTidakWhich 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…

Isi permintaan

NamaJenisWajibTentang apa ini
amount_minorintegerTidakOmit to refund everything still refundable on the deposit.
reasonstringTidak

Tanggapan

NamaJenisWajibTentang apa ini
quoted_minorintegerTidakWhat the customer asked to add, and what the screen promised them.
settled_minorinteger | nullTidakWhat actually arrived. **`null` = not known yet**, never zero.
fee_minorinteger | nullTidakWhat the provider kept out of the settlement. **`null` = not known**, never zero — recording an unknown as `0` would credit the customer the shortfall.
credited_minorintegerTidakWhat went into the balance — `settled_minor - fee_minor`.
shortfall_minorinteger | nullTidak`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>Tidak
is_autobooleanTidakWhether a standing instruction created this, rather than a person.
action_urlstringTidakWhere 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.
idUuidYaUUIDv7 identifier — sortable by creation time (docs/02 §8).
amount_minorintegerYa
currencystringYa
statusstring<pending, requires_action, captured, failed>Ya⛔ 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_minorintegerYa
refundable_minorintegerYaWhat is left to send back to the card. Zero unless it captured.
gatewaystringTidakThe provider's driver — `stripe`, `paypal`, `nowpayments`. ⛔ Never a credential and never a merchant-account reference: which account your provider banks with is their commercia…
errorstringTidakThe gateway's refusal, in words the customer can act on.
created_atstringYa
captured_atstring | nullTidak

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429