> ## Documentation Index > Fetch the complete documentation index at: https://developer.madhousewallet.com/llms.txt > Use this file to discover all available pages before exploring further. # Confirm a v2 transfer > After sending USDC on-chain to the `deposit_address` returned by `POST /api/payouts/transfer/v2`, call this endpoint with the `transfer_id` and the on-chain transaction hash (`tx_hash`). The platform will use the hash to match the incoming deposit to your transfer and automatically initiate the fiat payout to your recipient. **Important:** - Each `tx_hash` may only be used **once** across the entire platform. A hash that has already been associated with any transfer (including your own) is rejected with `409`. This prevents replay attacks. - A second call with the same `transfer_id` and the same `tx_hash` is idempotent — it returns the current status without error. - A second call with the same `transfer_id` but a different `tx_hash` is rejected with `409` — overwriting is not allowed. - Once the deposit is detected (status moves past `pending_match`), this endpoint returns the current status without making any changes. **Rate limit:** 20 requests/minute. ## OpenAPI ````yaml /openapi.json post /api/payouts/transfer/v2/confirm-transfer openapi: 3.0.3 info: title: MW Payouts API version: 1.0.0 description: >- The MW Payouts API lets you programmatically retrieve exchange-rate quotes, calculate platform fees, and submit USDC-to-fiat payout transfers on behalf of your account. All requests must be authenticated with an API key obtained from the **Developers** section of the dashboard. API keys are for **server-side use only** — never embed them in client-side code. contact: name: MW Support email: support@madhousewallet.com servers: - url: https://business.madhousewallet.com description: Production security: - BearerAuth: [] tags: - name: Payouts description: USDC-to-fiat payout operations - name: Recipients description: Payout recipient management paths: /api/payouts/transfer/v2/confirm-transfer: post: tags: - Payouts summary: Confirm a v2 transfer description: >- After sending USDC on-chain to the `deposit_address` returned by `POST /api/payouts/transfer/v2`, call this endpoint with the `transfer_id` and the on-chain transaction hash (`tx_hash`). The platform will use the hash to match the incoming deposit to your transfer and automatically initiate the fiat payout to your recipient. **Important:** - Each `tx_hash` may only be used **once** across the entire platform. A hash that has already been associated with any transfer (including your own) is rejected with `409`. This prevents replay attacks. - A second call with the same `transfer_id` and the same `tx_hash` is idempotent — it returns the current status without error. - A second call with the same `transfer_id` but a different `tx_hash` is rejected with `409` — overwriting is not allowed. - Once the deposit is detected (status moves past `pending_match`), this endpoint returns the current status without making any changes. **Rate limit:** 20 requests/minute. operationId: confirmTransferV2 requestBody: required: true content: application/json: schema: type: object required: - transfer_id - tx_hash properties: transfer_id: type: string description: >- The `transfer_id` returned by `POST /api/payouts/transfer/v2`. example: 507f1f77bcf86cd799439011 tx_hash: type: string description: >- On-chain transaction hash of your USDC send. EVM format: `0x` followed by 64 hex chars (32 bytes). Solana format: base58 signature (85–88 chars). example: >- 0xabc123def456abc123def456abc123def456abc123def456abc123def456abc1 example: transfer_id: 507f1f77bcf86cd799439011 tx_hash: >- 0xabc123def456abc123def456abc123def456abc123def456abc123def456abc1 responses: '200': description: tx_hash recorded or already processing content: application/json: schema: type: object required: - transfer_id - status - message properties: transfer_id: type: string description: The transfer ID. example: 507f1f77bcf86cd799439011 status: type: string enum: - awaiting_deposit - pending_match - processing - deposit_sent - transfer_created - completed - failed - refunded description: Current transfer status after recording the hash. example: pending_match message: type: string description: Human-readable summary of the action taken. example: >- tx_hash recorded — the system will match your deposit and initiate the payout automatically example: transfer_id: 507f1f77bcf86cd799439011 status: pending_match message: >- tx_hash recorded — the system will match your deposit and initiate the payout automatically '400': description: >- Invalid `transfer_id` format, invalid `tx_hash` format, or transfer is not a v2 transfer content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Transfer not found or not owned by your account content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: >- This `tx_hash` has already been used for another transfer, or a different `tx_hash` has already been recorded for this transfer content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Rate limit exceeded (20 requests/minute per key) content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: Error: type: object properties: error: type: string description: Human-readable error message required: - error securitySchemes: BearerAuth: type: http scheme: bearer description: >- Pass your API key as a Bearer token: `Authorization: Bearer mw_live__` ````