> ## Documentation Index > Fetch the complete documentation index at: https://docs.onswitch.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Lookup transaction > Get details of a single transaction by its reference (UUID). ## OpenAPI ````yaml /openapi.json get /wallet/{wallet_id}/transaction/{reference} openapi: 3.0.3 info: title: Receive stablecoin. Get fiat in seconds. description: Stablecoin collection and settlement layer. version: 1.0.0 contact: name: Switch Labs email: contact@onswitch.xyz license: name: Proprietary x-tagGroups: - name: Institution tags: - Institution - name: Miscellaneous tags: - Miscellaneous - name: History tags: - History - name: Payment tags: - Payment - name: Webhook tags: - Webhook - name: Offramp tags: - Offramp - name: Onramp tags: - Onramp - name: Swap tags: - Swap - name: Developer tags: - Developer - name: Wallet tags: - Wallet - name: Compliance tags: - Compliance servers: - url: https://api.onswitch.xyz description: Production server security: [] tags: - name: Institution description: Institution discovery and bank or payment-rail lookup - name: Miscellaneous description: Requirements, coverage, assets, confirmation, and transaction status - name: History description: Payment history and summaries for the partner's account - name: Payment description: Saved payment beneficiaries, payment confirmation, and status - name: Webhook description: Webhook delivery history and callback resend - name: Offramp description: Offramp transaction endpoints for converting stablecoins to local currency - name: Onramp description: Onramp transaction endpoints for converting local currency to stablecoins - name: Swap description: Swap endpoints for exchanging between different stablecoin assets - name: Developer description: Developer fee balance and withdrawal - name: Wallet description: >- Wallet endpoints for creating and managing chain abstracted stablecoin wallets - name: Compliance description: AML compliance screening for PEP, sanctions, and other regulatory reasons paths: /wallet/{wallet_id}/transaction/{reference}: get: tags: - Wallet summary: Lookup transaction description: Get details of a single transaction by its reference (UUID). operationId: lookupWalletTransaction parameters: - name: wallet_id in: path required: true description: Wallet ID (24-character hex) schema: type: string pattern: ^[a-f0-9]{24}$ - name: reference in: path required: true description: Transaction reference (UUID) schema: type: string format: uuid example: 064b519b-5087-d200-0000-00000000000e responses: '200': description: Transaction lookup successful content: application/json: schema: type: object required: - success - message - timestamp - data properties: success: type: boolean message: type: string timestamp: type: string format: date-time data: type: object nullable: true properties: reference: type: string format: uuid nullable: true description: Transaction reference (UUID) transaction_hash: type: string nullable: true description: Blockchain transaction hash explorer_url: type: string format: uri nullable: true description: URL to view transaction on blockchain explorer type: type: string description: Transaction type (e.g. transfer) date: type: string format: date-time nullable: true sender: type: string nullable: true receiver: type: string nullable: true status: type: string enum: - successful - failed - processing fee: type: object nullable: true properties: amount: type: number description: Total fee amount in USD assets: type: array items: type: object properties: id: type: string description: Asset ID (e.g. base:usdc) amount: type: number input: type: object nullable: true properties: amount: type: number assets: type: array items: type: object properties: id: type: string description: Asset ID (e.g. base:usdc) amount: type: number output: type: object nullable: true description: Output side of the transaction properties: amount: type: number assets: type: array items: type: object properties: id: type: string amount: type: number example: success: true message: Transaction lookup successful timestamp: '2026-04-18T14:22:08.631Z' data: reference: f891a3c2-5e7d-4b91-8f62-0c4d1e9a7365 transaction_hash: >- 0xd4c19f2e8a91b06357cef3049821ea47dc33a09ef12c8456f8ab2d9e0c7e51a3 explorer_url: >- https://basescan.org/tx/0xd4c19f2e8a91b06357cef3049821ea47dc33a09ef12c8456f8ab2d9e0c7e51a3 type: transfer date: '2026-04-18T14:19:41.208Z' sender: '0x8F3aC91d2B741E59f064E9053a4d2E8F1c0b6D93a' receiver: '0x42c9E1aF8d736B2D094e6590315Dc7a1F947c4B0e' status: successful fee: amount: 0.01 assets: - id: base:usdc amount: 0.01 input: amount: 10 assets: - id: base:usdc amount: 10 output: amount: 10 assets: - id: arbitrum:usdc amount: 10 '400': $ref: '#/components/responses/BadRequest' security: - ServiceKey: [] components: responses: BadRequest: description: Bad request - Invalid input parameters or validation error content: application/json: schema: type: object required: - success - message - timestamp properties: success: type: boolean example: false message: type: string description: Error message describing what went wrong timestamp: type: string format: date-time data: description: Additional error details nullable: true example: success: false message: amount must be greater than 0 for the selected corridor timestamp: '2026-04-18T14:22:08.631Z' data: null securitySchemes: ServiceKey: type: apiKey in: header name: x-service-key description: Service key for API authentication ````