marketplace

POST `/v1/marketplace/vendor/payout-methods`

Propose a destination to be paid at.

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

Kalitи API-ро ҳамчун token-и bearer фиристед. Ин нуқтаи ниҳоӣ дар мушаххасот иҷозати мушаххасеро нишон намедиҳад, бинобар ин ба калиди худ ҳадди ақали заруриро диҳед ва ба ҷои тахмин кардан, ҷавобро санҷед.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

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

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

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

Тафсилот

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.

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

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`rail`	`string`	Бале	—
`destination`	`string`	Не	Empty for account credit, which has nowhere to send.
`network`	`string`	Не	—
`label`	`string`	Не	—

Ҷавоб

Ном	Намуд	Талаб карда мешавад	Ин чӣ аст
`id`	`string`	Бале	—
`rail`	`string`	Бале	—
`rail_name`	`string`	Бале	—
`destination`	`string`	Бале	⛔ 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`	Бале	⛔ 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`	Бале	—
`state`	`MarketplacePayoutMethodState`	Бале	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`	Бале	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`	Не	—
`is_default`	`boolean`	Бале	—
`verified_at`	`string`	Не	—
`hold_until`	`string`	Не	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[]`	Бале	—

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

401 · 404 · 422

POST /v1/marketplace/vendor/payout-methods