---
title: "Get a transaction"
method: GET
path: "/v1/stablecoin/transactions/{id}"
tags: ["Transactions"]
---

# Get a transaction

`GET /v1/stablecoin/transactions/{id}`

Returns a single transaction by ID.

## Path parameters

- `id` string, uuid, required

## Response `200`

Transaction found

- Transaction
  - `id` string, uuid, required — Unique transaction identifier
  - `type` 'ISSUANCE' | 'REDEMPTION' | 'BRIDGE', nullable — Transaction type. Null while the transaction is `PENDING` (flexible redemption) and a destination has not yet been chosen.
  - `status` 'PROCESSING' | 'PENDING' | 'COMPLETED' | 'FAILED' | 'CANCELED', required — Current transaction status. `COMPLETED`, `FAILED`, and `CANCELED` are terminal. `CANCELED` currently applies to `ISSUANCE` transactions canceled before settlement. `PENDING` applies to flexible-redemption transactions awaiting approval via [Approve a pending redemption](#operation/updateTransactionDestination); `type` and `destination` are null until approved.
  - `amount` string, required — Transaction amount as a decimal string (e.g. "10000.00")
  - `token` 'RLUSD', required — Always RLUSD
  - `source` TransactionEndpoint, required
    - `type` 'FIAT' | 'CRYPTO', required — Endpoint type
    - `walletId` string, nullable — Wallet identifier (e.g. `RIP0000001`). Present when type is `CRYPTO`.
    - `address` string, nullable — The customer's on-chain address on this leg. Present when type is `CRYPTO` and the on-chain leg has been initiated. EVM addresses include the `0x` prefix.
    - `chain` string, nullable — Blockchain network name (e.g. XRPL, ETH). Present when type is `CRYPTO`.
    - `transactionHash` string, nullable — On-chain transaction hash for this leg. Present when type is `CRYPTO` and the on-chain leg has settled. EVM chains (e.g. ETH) return the hash with the `0x` prefix; XRPL hashes are uppercase hex without a prefix.
    - `counterpartyAddress` string, nullable — The Ripple-side internal account address that participated in this on-chain leg (the counterparty to your wallet). Present when type is `CRYPTO` and the on-chain leg has been initiated. EVM addresses include the `0x` prefix.
  - `destination` TransactionEndpoint
    - `type` 'FIAT' | 'CRYPTO', required — Endpoint type
    - `walletId` string, nullable — Wallet identifier (e.g. `RIP0000001`). Present when type is `CRYPTO`.
    - `address` string, nullable — The customer's on-chain address on this leg. Present when type is `CRYPTO` and the on-chain leg has been initiated. EVM addresses include the `0x` prefix.
    - `chain` string, nullable — Blockchain network name (e.g. XRPL, ETH). Present when type is `CRYPTO`.
    - `transactionHash` string, nullable — On-chain transaction hash for this leg. Present when type is `CRYPTO` and the on-chain leg has settled. EVM chains (e.g. ETH) return the hash with the `0x` prefix; XRPL hashes are uppercase hex without a prefix.
    - `counterpartyAddress` string, nullable — The Ripple-side internal account address that participated in this on-chain leg (the counterparty to your wallet). Present when type is `CRYPTO` and the on-chain leg has been initiated. EVM addresses include the `0x` prefix.
  - `createdAt` string, date-time, required — Timestamp when the transaction was created
  - `updatedAt` string, date-time, required — Timestamp when the transaction was last updated

## Other responses

- `401` — Missing or expired access token
- `403` — Insufficient scope for the requested operation
- `404` — Resource does not exist
- `500` — Unexpected server error

---

[API](https://skmtc.net/ripple/apis/ripple-mint-api.md) · [All operations](https://skmtc.net/ripple/apis/ripple-mint-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ripple/ripple-mint-api/versions/40f45c88957c/schema)