# Get a transaction

Returns a single transaction by ID.

Endpoint: GET /v1/stablecoin/transactions/{id}
Version: 1.0.0
Security: oauth2

## Path parameters:

  - `id` (string, required)
    Transaction UUID

## Response 200 fields (application/json):

  - `id` (string, required)
    Unique transaction identifier

  - `type` (string, required)
    Transaction type.
    Enum: "ISSUANCE", "REDEMPTION", "BRIDGE"

  - `status` (string, required)
    Current transaction status. COMPLETED, FAILED, and CANCELED are terminal.
CANCELED currently applies to ISSUANCE transactions canceled before settlement.
    Enum: "PROCESSING", "COMPLETED", "FAILED", "CANCELED"

  - `amount` (string, required)
    Transaction amount as a decimal string (e.g. "10000.00")

  - `token` (string, required)
    Always RLUSD
    Enum: "RLUSD"

  - `source` (object, required)

  - `source.type` (string, required)
    Endpoint type
    Enum: "FIAT", "CRYPTO"

  - `source.walletId` (string,null)
    Wallet identifier (e.g. RIP0000001). Present when type is CRYPTO.

  - `source.address` (string,null)
    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.

  - `source.chain` (string,null)
    Blockchain network name (e.g. XRPL, ETH). Present when type is CRYPTO.

  - `source.transactionHash` (string,null)
    On-chain transaction hash for this leg. Present when 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.

  - `source.counterpartyAddress` (string,null)
    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` (object, required)

  - `createdAt` (string, required)
    Timestamp when the transaction was created

  - `updatedAt` (string, required)
    Timestamp when the transaction was last updated

## Response 401 fields (application/problem+json):

  - `type` (string)
    URI reference identifying the problem type

  - `title` (string)
    Short, human-readable summary of the problem

  - `status` (integer)
    HTTP status code

  - `code` (string)
    Machine-readable error code
    Enum: "TRANSACTION_NOT_FOUND", "INVALID_REQUEST_BODY", "UNKNOWN_EXCEPTION"