---
title: "Get a transfer status"
method: GET
path: "/transfers/{shinkansen_id}/status"
tags: ["Transactions & Responses"]
---

# Get a transfer status

`GET /transfers/{shinkansen_id}/status`

## Request

- Base URL: `https://sandbox-gateway.shinkansen.finance/api`
- URL: `https://sandbox-gateway.shinkansen.finance/api/transfers/{shinkansen_id}/status`
- Auth: API key in header `Shinkansen-Api-Key`

Returns the current state of an **outbound transfer** and its **full reversal
history** as stored in the Gateway. This endpoint queries gateway state only;
it does not send a live consult to the switch network.

Use it when the participant needs to confirm transfer and reversal outcomes
(for example after a webhook timeout or during SAF retries). The root-level
`reversed` boolean indicates whether the transfer was effectively reversed;
`reversals` lists every reversal attempt with its own status and CCA response.

## Response `200`

The current status and detail of a transfer in the Gateway API, including transfer fields at the root, the `reversed` flag, and the full `reversals` history.

- TransactionStatusTransfers: Current state of an outbound transfer in the Gateway, including the full reversal history. Transfer fields are returned at the root of the object. Use `reversed` to know whether the transfer was effectively reversed without scanning `reversals`.
  - `transaction_id` string, uuid, required: Participant transaction ID (the ID sent in the original transfer request).
  - `shinkansen_transaction_id` string, uuid, required: Shinkansen internal transaction ID (returned as `shinkansen_transaction_id` in the transfer ACK).
  - `status` 'pending' | 'ok' | 'error', required: Gateway transaction status.
  - `response_status` string, nullable, required: Network response code for the transfer (for example `approved`), or `null` while pending. See [Response codes](https://docs.shinkansen.tech/reference/response-codes).
  - `amount` string, required: Transfer amount.
  - `currency` string, required: Currency code.
  - `reference` string, nullable, required: Transfer reference from the original request.
  - `tracenumber` string, nullable, required: IFO trace number (12-digit string), when available.
  - `switch_timestamp` string, nullable, required: Local Chile timestamp from the switch/CCA for the transfer, when available.
  - `gateway_timestamp` string, date-time, required: UTC timestamp when the gateway accepted the transfer.
  - `reversed` boolean, required: `true` when at least one reversal for this transfer was **applied** (`status` `ok` / approved by CCA). `false` when there are no reversals, or every reversal is still `pending` or ended in `error`. Clients should use this field instead of inferring reversal outcome from `reversals`.
  - `reversals` TransferStatusReversalItem[], required: Full reversal history for the transfer (any status), ordered oldest first. Multiple entries may exist when the participant retries reversals (for example SAF).
    - `reversal_id` string, uuid, nullable: Participant reversal ID from the reversal request, if provided.
    - `shinkansen_reversal_id` string, uuid: Shinkansen internal reversal transaction ID.
    - `reversal_type` string: Reversal reason code (for example `reversal_conditional`).
    - `status` 'pending' | 'ok' | 'error': Gateway reversal status.
    - `response_status` string, nullable: CCA response code for this reversal attempt (for example `approved` or `error_reversal_max_time_conditional`), or `null` while the reversal is still pending. See [Response codes](https://docs.shinkansen.tech/reference/response-codes).
    - `tracenumber` string, nullable: Trace number associated with the reversal (same ISO identifier family as the original transfer), when available.
    - `received_at` string, date-time: UTC timestamp when the gateway recorded the reversal request.
    - `switch_timestamp` string, nullable: Local Chile timestamp from CCA for this reversal response, when available.

## Other responses

- `400`: Message received but rejected by Shinkansen Gateway due to validation errors
- `401`: Message received but rejected by Shinkansen Gateway due to an unauthorized access to the API Key or the JWS Signature
- `404`: Shinkansen transaction id not found in the Gateway API records.

---

[API](https://skmtc.dev/shinkansen/apis/transfers-shinkansen-endpoints.md) - [All operations](https://skmtc.dev/shinkansen/apis/transfers-shinkansen-endpoints/llms.txt) - [OpenAPI document](https://skmtc.dev/shinkansen/apis/transfers-shinkansen-endpoints/revisions/76363158582b?raw)