marketplace
POST /v1/marketplace/vendor/payout-methods
Propose a destination to be paid at.
Pengesahan
Hantar kunci API sebagai token pembawa. Titik akhir ini tidak menyatakan kebenaran tertentu dalam spesifikasi, jadi berikan kunci anda kebenaran minimum yang diperlukan dan semak respons tersebut daripada membuat andaian.
Titik akhir ini tidak memerlukan id organisasi. Kunci anda telah mengenal pasti organisasi kepunyaannya, dan respons dis skopkan kepadanya.
Cuba
Gantikan apa sahaja di dalam kurungan sudut dengan nilai anda sendiri, dan pemegang tempat kunci dengan kunci dari papan pemuka anda.
curl -X POST https://api.zinndigital.com/v1/marketplace/vendor/payout-methods \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "rail": <string> }'Sudah log masuk? Konsol API dalam papan pemuka anda mengisi id organisasi sebenar dan kunci anda sendiri, serta menjalankan permintaan terhadap API langsung supaya anda boleh melihat respons sebenar. Buka penamat ini dalam konsol API
Butiran
docs/82 §7c. The row is created **unverified** and can receive nothing: only staff verification makes it payable, and then only after the 48-hour cooling-off. ⛔⛔ **A change of destination is a new row, never an edit** — there is deliberately no endpoint that changes `destination` on an existing one. §7c: *"Change of payout details is the account-takeover cash-out route, and must be treated as one."* Editing a verified row would keep its verified state and its long-expired hold while pointing the money somewhere nobody looked at. ⭐ Re-adding a destination the seller already has returns the existing row rather than minting a second one — otherwise "change it and change it back" resets the cooling-off clock in two requests. ⛔ The **network** is its own field, not part of the address. Sending USDT TRC20 to a BEP20 address loses the money irrecoverably, so the same address on two networks is two destinations, each earning its own proof and its own hold.
Badan permintaan
| Nama | Jenis | Diperlukan | Apakah ia |
|---|---|---|---|
rail | string | Ya | — |
destination | string | Tidak | Empty for account credit, which has nowhere to send. |
network | string | Tidak | — |
label | string | Tidak | — |
Respons
| Nama | Jenis | Diperlukan | Apakah ia |
|---|---|---|---|
id | string | Ya | — |
rail | string | Ya | — |
rail_name | string | Ya | — |
destination | string | Ya | ⛔ **Masked, always.** Enough to recognise which account this is, never enough to reproduce it. The whole value never leaves the engine on a read path. |
network | string | Ya | ⛔ Its own field, never folded into the address. Sending USDT TRC20 to a BEP20 address loses the money irrecoverably (docs/82 §7b), so the network is part of the destination's id… |
label | string | Ya | — |
state | MarketplacePayoutMethodState | Ya | Where one destination is in its own verification (docs/82 §7c). `retired` rows are kept rather than deleted — a payout that went there is explained by them. |
proof_kind | MarketplacePayoutProofKind | Ya | How ownership of the destination was shown. ⛔ Crypto is the honest exception and is recorded as one: docs/82 §7c states that *no document can prove wallet ownership*, so a signe… |
rejection_reason | string | Tidak | — |
is_default | boolean | Ya | — |
verified_at | string | Tidak | — |
hold_until | string | Tidak | docs/82 §7c's 48-hour cooling-off on the **first** payout to this destination — long enough for the change notice to land, short enough that a seller who genuinely changed bank… |
permitted_proof_kinds | MarketplacePayoutProofKind[] | Ya | — |
Ralat yang boleh dikembalikan oleh titik akhir ini
401 · 404 · 422