Skip to main content

​
What happened

A deposit arrived from an address that required sender information before Conduit could credit it. The required details were not submitted before the deadline, so the deposit was not credited and is now in a terminal failed state with failureCode: SENDER_INFO_TIMEOUT. In production the deadline is 30 days from the first transaction.awaiting_sender_information event. In sandbox the deadline is compressed to approximately 30 seconds by default. 
{
  "type": "SENDER_INFO_TIMEOUT",
  "title": "Sender information deadline expired",
  "status": 422,
  "detail": "The sender-information gate timed out before the required Travel Rule details were provided.",
  "resolution": "Submit the deposit again with the sender details included up front.",
  "docs": "/errors#sender-info-timeout",
  "instance": "/v2/transactions/txn_abc123/sender-information",
  "correlationId": "corr_xyz789",
  "timestamp": "2026-01-15T09:30:00.000Z"
}

​
Common causes

  • No sender-information workflow — the integration did not handle transaction.awaiting_sender_information events and never submitted the required details
  • Missed deadline — the sender-information endpoint was called after the 30-day production window expired
  • Sandbox timing — the deposit was created in sandbox and the compressed ~30-second deadline elapsed before the simulate endpoint was called

​
Recovery

This is a terminal state. The deposit cannot be recovered; no funds were credited to the customer.
1. Confirm the terminal state Read the transaction to confirm it is terminal: 
curl -X GET https://api.conduit.financial/v2/transactions/txn_abc123 \
  -H "x-api-key: YOUR_API_KEY"
The response will show status: "failed" and failureCode: "SENDER_INFO_TIMEOUT". 2. Notify the sender The underlying crypto deposit was received on-chain but not credited. The sender should be notified so they can initiate a new transfer. Include sender information with the new transfer if the same corridor triggers the gate again. 3. Pre-supply sender information on the next deposit If your integration controls when sender information is submitted, use the POST /v2/transactions/:id/sender-information endpoint immediately on receiving transaction.awaiting_sender_information: 
curl -X POST https://api.conduit.financial/v2/transactions/txn_new123/sender-information \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "originator": {
      "entityType": "INDIVIDUAL",
      "firstName": "Jane",
      "lastName": "Doe",
      "dateOfBirth": "1990-01-01",
      "countryOfCitizenship": "USA"
    }
  }'

​
Prevention

  • Handle transaction.awaiting_sender_information immediately — configure a webhook listener and submit the sender details as soon as the event arrives; do not rely on a later batch job
  • Build a fallback reminder — if the initial submission fails, use the daysRemaining field on the event to schedule a follow-up before the deadline
  • Sandbox: use the simulate endpoint — drive the sandbox sender-info gate before the compressed deadline expires
Two events are relevant to this failure path: transaction.awaiting_sender_information fires when Conduit parks the deposit at the sender-information gate. The payload includes a daysRemaining field (null once the deadline has passed): 
{
  "type": "transaction.awaiting_sender_information",
  "data": {
    "transactionId": "txn_abc123",
    "daysRemaining": 29
  }
}
transaction.failed fires when the gate expires: 
{
  "type": "transaction.failed",
  "data": {
    "transactionId": "txn_abc123",
    "failureCode": "SENDER_INFO_TIMEOUT"
  }
}