---
title: "Receives responses"
method: POST
path: "/responses"
tags: ["Participant Webhooks"]
---

# Receives responses

`POST /responses`

Webhook for receiving responses (here receives 0210 (Transfer Response) and 0430 (Reversal Response) messages). The response is sent after the transfers/reversals have been received by the Gateway from the Switch (CCA).

## Request body

- ParticipantResponseMessage — Responses to transfers, sent by Shinkansen to the Participant
  - `document` object, required — Envelops the message content
    - `header` TransferFwMessageHeader, required — Header for original transfer messages
      - `shinkansen_message_id` string, uuid, required — UUID Unique identifier of the message. Generated by Shinkansen initiating the transactions (or sending the responses) inside this message. UUID format is required.
      - `creation_date` string, date-time, required — Creation date of the message in ISO 8601 format. Generated by Shinkansen initiating the transactions (or sending the responses) inside this message.
      - `sender` string, required — Shinkansen sending this message. For forwarded transfers, responses or reversals.
      - `receiver` string, required — The receiver of this message for this case, the Participant (your financial institution)
    - `responses` TransactionResponse[] — One or more transfer responses (one per transaction).
      - `transaction_type` 'transfer' | 'reversal', required — The type of transaction. For the transfer product it's always "transfer".
      - `transaction_id` string, uuid, required — The transaction ID that was included in the original request sent to Shinkansen.
      - `shinkansen_transaction_id` string, uuid, required — The transaction ID assigned by Shinkansen.
      - `shinkansen_transaction_status` 'ok' | 'error' | 'pending', required — The status of the transaction as assigned by Shinkansen. It can be one of the following: - `ok`: The transaction was successful - `error`: The transaction failed. - `pending`: The transaction is pending. (for consultation purposes)
      - `shinkansen_response_id` string, uuid, required — The unique ID associated with this response in the Shinkansen network.
      - `response_status` 'approved' | 'error_reversal_insufficient_balance' | 'error_creditor_account_over_limits' | 'error_creditor_account_not_found' | 'error_creditor_fi_offline' | 'error_creditor_fi_timeout' | 'error_creditor_account_closed' | 'error_creditor_rut_invalid' | 'error_ifr_service_unavailable', required — This is a reduced list of the possible responses from the underlying network. The complete list can be found in the [Shinkansen documentation](https://docs.shinkansen.tech/reference/response-codes). * `approved`: Approved Transaction/Reversal * `error_reversal_insufficient_balance`: Rejected due to insufficient balance. (for reversals) * `error_creditor_account_over_limits`: Destination account restricted for deposits. * `error_creditor_account_not_found`: Destination account not found. * `error_creditor_fi_offline`: IFR host unavailable. * `error_creditor_fi_timeout`: Timeout at destination bank. * `error_creditor_account_closed`: Destination account is closed. * `error_creditor_rut_invalid`: Invalid beneficiary RUT. * `error_ifr_service_unavailable`: Unspecified error.
      - `response_message` string, required — A message further describing the status of the transaction from the underlying network.
      - `network_metadata` object — The network metadata contains information about the transaction as reported by the underlying network. It is optional and may not be present in all cases.
        - `operation_timestamp` string — The timestamp of the transaction as reported by the underlying network. Santiago time zone (Chile).
        - `authorization_code` string — The authorization code generated by IFR financial institution composed of 6 digits.
        - `response_code` string — Response code from the underlying network (ISO 0210/0430). Same value as reported by CCA.
        - `reversal_indicator` string — Reversal indicator from consult responses (0210 consult). Present only when the response corresponds to a transfer status consultation.

## Response `200`

Message correctly received and accepted to be processed by Participant, this is a notification with the status of the transaction. If you dont receive the status oportuniy, you can request the status of the transaction in our endpoint (https://docs.shinkansen.tech/reference/get-transaction-status-by-id-3).

- StatusAcceptedFwTransferResponse — Status accepted response HTTP 200
  - `message_id` string, uuid, required — Message ID generated by Participant receiving the response
  - `responses` object[], required — Array of mappings between original response_id and shinkansen_response_id
    - `response_id` string, uuid, required — The response_id - Generated by the Participant (your internal identifier for the response).
    - `shinkansen_response_id` string, uuid, required — The original shinkansen_response_id - Generated by Shinkansen

## Other responses

- `400` — Invalid message (e.g: invalid payload) - Maybe you want to respond with detailed error message for tracking purposes
- `401` — Invalid signature JWS (e.g: invalid certificate or expired)
- `409` — Duplicate message or transaction ID (e.g: Send same message twice)

---

[API](https://skmtc.net/shinkansen/apis/payouts-shinkansen-endpoints.md) · [All operations](https://skmtc.net/shinkansen/apis/payouts-shinkansen-endpoints/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/shinkansen/payouts-shinkansen-endpoints/versions/1e4a6760b7e8/schema)