Confirm a v2 transfer

curl --request POST \
  --url https://business.madhousewallet.com/api/payouts/transfer/v2/confirm-transfer \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "transfer_id": "507f1f77bcf86cd799439011",
  "tx_hash": "0xabc123def456abc123def456abc123def456abc123def456abc123def456abc1"
}
'

{
  "transfer_id": "507f1f77bcf86cd799439011",
  "status": "pending_match",
  "message": "tx_hash recorded — the system will match your deposit and initiate the payout automatically"
}

Payouts

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.

POST

/

api

/

payouts

/

transfer

/

v2

/

confirm-transfer

Confirm a v2 transfer

curl --request POST \
  --url https://business.madhousewallet.com/api/payouts/transfer/v2/confirm-transfer \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "transfer_id": "507f1f77bcf86cd799439011",
  "tx_hash": "0xabc123def456abc123def456abc123def456abc123def456abc123def456abc1"
}
'

{
  "transfer_id": "507f1f77bcf86cd799439011",
  "status": "pending_match",
  "message": "tx_hash recorded — the system will match your deposit and initiate the payout automatically"
}

Authorizations

Authorization

string

header

required

Pass your API key as a Bearer token: Authorization: Bearer mw_live_<keyId>_<secret>

Body

application/json

transfer_id

string

required

The transfer_id returned by POST /api/payouts/transfer/v2.

Example:

"507f1f77bcf86cd799439011"

tx_hash

string

required

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"

Response

tx_hash recorded or already processing

transfer_id

string

required

The transfer ID.

Example:

"507f1f77bcf86cd799439011"

status

enum<string>

required

Current transfer status after recording the hash.

Available options:

awaiting_deposit,

pending_match,

processing,

deposit_sent,

transfer_created,

completed,

failed,

refunded

Example:

"pending_match"

message

string

required

Human-readable summary of the action taken.

Example:

"tx_hash recorded — the system will match your deposit and initiate the payout automatically"

Create a v2 transfer Get a transfer

⌘I