reseller
POST /v1/reseller/client-wallets/top-ups/{topUpId}/refunds
Send a deposit back to the card it came from.
認証
ベアラー トークンとして API キーを送信します。キーには reseller.manage 権限が付与されている必要があります。権限のないキーは 404 ではなく 403 で拒否されます。
組織 ID を入力する場所
このエンドポイントはクエリパラメータとして org_id を受け取ります。省略した場合はテナントサブツリー全体が対象になり、指定した場合は特定の組織のみに絞り込まれます。
組織IDは、ダッシュボードのAPIキー画面にキーのすぐ横に表示されています。これは、実行するすべての呼び出しで同じIDになります。
試してみる
アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。
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 '{ }'ログインしていますか？ダッシュボード内のAPIコンソールでは、実際の組織IDやお客様ご自身のキーが自動入力され、ライブ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… |
リクエスト本文
| 名前 | タイプ | 必須 | これがその内容です |
|---|---|---|---|
amount_minor | integer | いいえ | Omit to refund everything still refundable on the deposit. |
reason | string | いいえ | — |
返信
| 名前 | タイプ | 必須 | これがその内容です |
|---|---|---|---|
quoted_minor | integer | いいえ | What the customer asked to add, and what the screen promised them. |
settled_minor | integer | null | いいえ | What actually arrived. null = not known yet, never zero. |
fee_minor | integer | 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_minor | integer | いいえ | What went into the balance — settled_minor - fee_minor. |
shortfall_minor | integer | 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… |
purpose | string<general, ai> | いいえ | — |
is_auto | boolean | いいえ | Whether a standing instruction created this, rather than a person. |
action_url | string | いいえ | 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. |
id | Uuid | はい | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
amount_minor | integer | はい | — |
currency | string | はい | — |
status | string<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_minor | integer | はい | — |
refundable_minor | integer | はい | What is left to send back to the card. Zero unless it captured. |
gateway | string | いいえ | The provider's driver — stripe, paypal, nowpayments. ⛔ Never a credential and never a merchant-account reference: which account your provider banks with is their commercial… |
error | string | いいえ | The gateway's refusal, in words the customer can act on. |
created_at | string | はい | — |
captured_at | string | null | いいえ | — |
このエンドポイントが返すエラー
401 · 403 · 404 · 422 · 429