Deposit instructions
GET /v2/deposit-instructions
List fiat deposit instructions
Where to send a BANK TRANSFER to fund this account in CLP. The fiat counterpart of GET /v2/deposit-addresses, which covers crypto.
The transfer must come from a bank account in your own name and RUT. Skipo matches an incoming transfer to an account by the originator RUT the bank reports — there is no reference code, no memo and no per-customer account number. A transfer sent from anyone else's account cannot be matched and is NOT credited, and recovering it is a manual support case. Check the RUT Skipo holds for you with GET /v2/account (nationalId).
Skipo publishes more than one account. They are interchangeable — a deposit into any of them credits the same balance. Prefer the one at your own bank: a same-bank transfer in Chile settles faster and costs less than an interbank one.
CLP only. There is no USD bank account, so this never returns one; crypto funding is GET /v2/deposit-addresses. Amounts are not here — minimumDeposit is on GET /v2/assets.
Responses
| Code | Description | Body |
|---|---|---|
200 | Success. | object |
401 | application/problem+json (RFC 9457) — branch on code, not on the status: unauthorized (not retryable), key_expired (not retryable), key_revoked (not retryable). | — |
403 | application/problem+json (RFC 9457) — branch on code, not on the status: insufficient_scope (not retryable), ip_not_allowed (not retryable), api_access_disabled (not retryable). | — |
429 | application/problem+json (RFC 9457) — branch on code, not on the status: rate_limited (retryable). | — |
500 | application/problem+json (RFC 9457) — branch on code, not on the status: internal_error (retryable). | — |
502 | application/problem+json (RFC 9457) — branch on code, not on the status: downstream_unavailable (retryable). | — |
503 | application/problem+json (RFC 9457) — branch on code, not on the status: maintenance (retryable). | — |
Schemas
BankDepositInstructionResource
| Field | Type | Description |
|---|---|---|
assetSymbol | string | Currency this account accepts. CLP only today. e.g. CLP. |
accountHolder | string | null | Account holder name, exactly as the receiving bank has it. e.g. Skipo Chile SpA. |
accountHolderNationalId | string | null | The RUT of the account HOLDER — Skipo's, not yours. It identifies the destination; it is not the RUT the transfer has to come from. See mustMatchSenderNationalId. e.g. 77.777.777-7. |
bankName | string | null | e.g. Banco de Chile. |
accountType | string | null | e.g. Cuenta Corriente. |
accountNumber | string | null | e.g. 00-123-45678-90. |
accountEmail | string | null | Email some Chilean banks require on the transfer form. e.g. deposits@skipo.com. |
mustMatchSenderNationalId | boolean | Always true, and the single most important field on this resource. The transfer MUST come from a bank account held in YOUR OWN name, under the same nationalId that GET /v2/account reports (in Chile, your RUT). Skipo matches an incoming transfer to an account by the originator RUT the bank reports, and there is no reference code, no memo and no per-customer account number to fall back on. ⚠️ A transfer from a third party — a company account for a personal balance, a partner, a payment processor, a friend — CANNOT be matched and is NOT credited. Recovering it is a manual support case, not an automatic return. This is the fiat equivalent of omitting a destination tag on a crypto deposit. e.g. true. |
Problem
| Field | Type | Description |
|---|---|---|
type | string | Stable problem-type URI. Resolves to docs for this error. e.g. https://docs.skipo.com/errors/rate_limited. |
title | string | Short, human-readable summary (stable, English). e.g. Rate limit exceeded. |
status | number | HTTP status code. e.g. 429. |
code | string | Stable machine-readable error code (equals the last path segment of type). e.g. rate_limited. |
retryable | boolean | Whether retrying the identical request may succeed. e.g. true. |
detail (optional) | string | Human-readable, possibly localized detail. |
instance (optional) | string | The request path that produced the error. |
traceId (optional) | string | Trace id — joins BigQuery api_request and Cloud Logging. |
Back to the endpoint reference. See also: Pagination · Errors · Ids and correlation.