Transfer RFIs and action_required status

Handle transfer RFIs when a transfer moves to action_required and Due needs additional information before processing can continue.

When this happens

A transfer may move to action_required when Due needs more information to complete review. This is usually a request for information (RFI) related to the transfer, source of funds, or supporting documentation.

You can detect this state in either of these ways:

1. Listen for the transfer.status_changed webhook event and check whether the transfer status changed to action_required.
2. Check the transfer with a GET request if the transfer has been pending for too long.

GET /v1/transfers/{transfer_id}

Webhook event to listen for

Subscribe your webhook endpoint to the transfer.status_changed event.

{
  "url": "https://example.com/webhooks/due",
  "events": ["transfer.status_changed"],
  "description": "Transfer status updates"
}

When Due sends the event, inspect the transfer object in data and start the RFI flow when data.status is action_required.

{
  "id": "wh_evt_xxx",
  "type": "transfer.status_changed",
  "data": {
    "id": "tf_xxx",
    "ownerId": "acct_xxx",
    "status": "action_required"
  },
  "occurredAt": "2025-09-22T12:00:00Z",
  "attemptedAt": "2025-09-22T12:00:00Z"
}

Information usually required

When a transfer is in action_required, Due may ask for one or more of the following:

• The purpose or nature of the transfer
• The source of funds
• Supporting documentation

The exact information needed depends on the transfer and review requirements.

Current RFI flow

Today, RFI responses are handled manually through Slack.

1. Detect that the transfer status is action_required.
2. Open a Slack thread with:
   • Account ID
   • Transfer ID
   • Extra information requested
   • Any available supporting context or documents
3. Tag @Cami Bitler in the thread.
4. Due reviews the information and resolves the RFI.

Example Slack message:

Account ID: acct_xxx
Transfer ID: tf_xxx
Status: action_required

Requested information:
- Purpose or nature of the transfer
- Source of funds
- Supporting documentation attached

@Cami Bitler

Upcoming API flow

Due is working on API endpoints for submitting RFI data directly. These endpoints will work similarly to the existing KYC submission flow, where required information and documents can be submitted through the API.

Until those endpoints are released, continue using the Slack workflow above for transfers in action_required.

This guide will be updated when the API-based RFI submission flow is implemented and released.