Requests for Information (RFI's)

Overview

A Request for Information (RFI) is how Bridge asks for additional information needed to complete a compliance or risk review. An RFI may concern your developer account, a customer, or specific transaction activity. Bridge RFI’s fall into two categories:

Customer RFI’s concern customer-level compliance reviews, including KYC, KYB, and enhanced due diligence.
Transaction RFI’s concern specific transaction activity that requires compliance or risk review.

This page outlines how Bridge’s RFI’s work and tools for managing them effectively.

Customer RFI’s vs Transaction RFI’s

	Customer RFI’s	Transaction RFI’s
What they cover	Customer-level compliance reviews, including KYC, KYB, and EDD	Specific transaction activity requiring compliance, risk, fraud, or banking-partner review
When they may occur	During onboarding, enhanced due diligence, post-onboarding follow-up, or an ongoing review	When transaction activity is flagged, additional context is required, or a banking partner requests information
Common requests	Proof of address, source of funds or wealth, business or ownership documents, government identification, account purpose, or clarification of customer information	Transaction purpose, sender and recipient relationship, source-of-funds evidence, name-mismatch explanations, invoices, receipts, contracts, or bank statements
Primary recipient	End customer or developer depending on the predefined developer communication settings	The developer by default. In limited cases, Bridge can send the RFI directly to the end customer at the developer’s request
Delivery channel	Email to the developer or directly to the end customer	Email, Slack, or the Bridge Dashboard, depending on the developer’s configured preference. Slack is the default
Who gathers the information	The developer or end customer provides the requested information directly to Bridge	The developer generally gathers any necessary information from its customer and submits it to Bridge. If direct customer delivery is enabled, the customer responds directly
What may be pending	Customer onboarding or another customer-level compliance review	The affected transaction, which may appear as `in_review` or otherwise remain paused

Responding to RFI’s

These RFI’s should be responded to as follows:

Customer RFI sent to the developer: The developer should collect any necessary information from its customer and reply to the RFI email.
Customer RFI sent directly to the customer: The customer should reply to the original RFI email and follow any secure document-upload instructions.
Transaction RFI sent to the developer: The developer should collect any necessary information from its customer and submit it through the Bridge Dashboard Support tab, reply to the original RFI email, or respond via API.
Transaction RFI sent directly to the customer: The customer should reply to the original RFI email and follow any secure document-upload instructions.

Answer each requested item and include the requested supporting documents. Submit sensitive information only through the secure response method identified in the RFI.

RFI API

The RFI API is in beta and currently only covers transaction RFIs, not customer RFIs. The API payloads described in this section are subject to change.

Use the RFI’s API to read the current state of RFI’s raised on your developer or customer accounts.

GET /rfis - list RFI’s, optionally filtered by state or customer_id, with cursor-based pagination via starting_after/ending_before. The limit parameter controls page size (default 10, min 1, max 100). Out-of-range values return 422.
GET /rfis/{rfiID} - retrieve a single RFI by id.

Request

curl --request GET \
  --url 'https://api.bridge.xyz/v0/rfis/8991c31c-3cf6-4128-8ad4-177fcd114c8a' \
  --header 'Api-Key: <api-key>'

Response

{
  "id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
  "state": "on_developer",
  "customer_id": "80b4cf5b-d4d0-4139-b8d8-de534e455cd3",
  "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
  "referent_type": "transfer",
  "bridge_action_taken": "transaction_paused",
  "expected_action_on_expiry": "pause_customer",
  "deadline": "2026-09-16T09:00:00Z",
  "dashboard_url": "https://dashboard.bridge.xyz/app/support?action=view-ticket&conversationId=d9c99009-edaf-4e2f-8b4e-389173655c8a",
  "state_changed_at": "2026-09-09T18:23:01Z",
  "additional_context": "Please provide documentation showing the origin of these funds.",
  "requested_items": [
    {
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "status": "requested",
      "content": "What is the purpose of this payment and how will the customer be using these funds?",
      "referent_type": "transfer",
      "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
      "response_types": ["free_text_explanation", "document_list"],
      "group_id": null
    },
    {
      "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
      "status": "requested",
      "content": "What is the source of funds for this payment? Please provide supporting documentation (bank or investment statement, pay stub, invoice, receipt or contract).",
      "referent_type": "transfer",
      "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
      "response_types": ["free_text_explanation", "document_list"],
      "group_id": null
    }
  ],
  "requested_item_groups": [],
  "created_at": "2026-09-09T18:23:01Z"
}

Responding to Requested Items

Use POST /v0/rfis/{id}/responses to submit answers to one or more requested items in a single atomic batch. All responses succeed or all fail together — a validation error on any item rolls back the entire request. Required scope: customer:write

Request

curl --request POST \
  --url 'https://api.bridge.xyz/v0/rfis/8991c31c-3cf6-4128-8ad4-177fcd114c8a/responses' \
  --header 'Api-Key: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
    "responses": [
      {
        "requested_item_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "free_text_explanation": "Personal savings accumulated over several years."
      }
    ]
  }'

Response types

response_types on each requested item is an array of strings listing the field names Bridge will accept in the request body. Use the string value directly as the field name when constructing your response — for example, if response_types contains "date", populate a date field. Possible values: text, text_list, date, address, identifying_information_list, document_list, boolean, free_text_explanation. Most items have a single entry. Some items accept more than one kind — you can submit any or all of them in one request.

Response fields

A single plain-text string. Used for name fields, description fields, and other single-value text.

"text": "Jane"

An array of plain-text strings. Used for multi-value fields such as nationalities or operating countries.

"text_list": ["USA", "GBR", "DEU"]

An ISO 8601 date string (YYYY-MM-DD).

"date": "1990-06-15"

A single postal address object.

"address": {
  "street_line_1": "123 Main St",
  "street_line_2": "Apt 4B",
  "city": "San Francisco",
  "subdivision": "CA",
  "postal_code": "94105",
  "country": "USA"
}

Field	Description
`street_line_1`	Primary street line.
`street_line_2`	Secondary street line (apartment, suite, floor, etc.). Optional.
`city`	City or locality.
`subdivision`	State, province, or first-level subdivision code (e.g. `CA`).
`postal_code`	Postal or ZIP code.
`country`	ISO 3166-1 alpha-3 country code (e.g. `USA`).

A plain true or false value. false is a valid answer.

"boolean": true

One or more identity documents or tax identification numbers.The valid values for type depend on the specific item:

Tax identification number items: use TIN types ssn, ein, itin, cpf, vat, or other. Passing a government-ID type returns 400.
Government ID document items: use ID types passport, drivers_license, national_id, residence_permit, ekyc, or other. Passing a TIN-only type returns 400.

// Tax identification number
"identifying_information_list": [
  { "type": "ssn", "issuing_country": "USA", "number": "123-45-6789" }
]

// Government-issued ID
"identifying_information_list": [
  {
    "type": "passport",
    "issuing_country": "USA",
    "number": "A12345678",
    "expiration": "2030-12-31",
    "image_front": "data:image/jpeg;base64,/9j/4AAQ...",
    "image_back": "data:image/jpeg;base64,/9j/4AAQ..."
  }
]

Field	Description
`type`	Document type discriminator. See above for valid values by item type.
`issuing_country`	ISO 3166-1 alpha-3 country that issued the document.
`number`	Document or identification number.
`expiration`	Document expiration date (`YYYY-MM-DD`). Optional.
`image_front`	Required for government ID types; optional for TIN types. Base64 data-URI (`data:image/[type];base64,[contents]`). Min 200×200px. Max 15MB. Valid types: `.pdf`, `.jpeg`, `.jpg`, `.png`, `.heic`, `.tif`. Combined size of `image_front` + `image_back` must not exceed 24MB.
`image_back`	Back-side image. Same format and constraints as `image_front`. Optional.

One or more file attachments. Files must be submitted as base64 data-URIs: data:<mime-type>;base64,<base64-encoded-content>.For selectable entity detail items, the document purpose is derived automatically and purposes may be omitted. For free-text items, purposes is required.

"document_list": [
  {
    "file": "data:application/pdf;base64,JVBERi0xLjQK...",
    "description": "Bank statement Jan–Sep 2026",
    "purposes": ["proof_of_source_of_funds"]
  }
]

Field	Description
`file`	Base64 data-URI (`data:image/[type];base64,[contents]`). Min 200×200px. Max 24MB. Valid types: `.pdf`, `.jpeg`, `.jpg`, `.png`, `.heic`, `.tif`.
`description`	Human-readable label for the document. Optional.
`purposes`	Array of document purpose strings. Required for free-text items; may be omitted for selectable entity detail items.

A plain-text explanation. Can be used as a primary response or as a supplement alongside another field. Maximum 3,000 characters; exceeding this limit returns 422.

"free_text_explanation": "The address above is my primary residence since 2019."

Submitting multiple kinds at once

When an item’s response_types has more than one entry, you can include more than one field in the same response object. Bridge processes all submitted kinds. Submitting a field not listed in response_types for a given item returns 400.

{
  "requested_item_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "text": "Jane",
  "document_list": [
    { "file": "data:application/pdf;base64,JVBERi0x...", "description": "ID document" }
  ]
}

Full example

{
  "responses": [
    {
      "requested_item_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "free_text_explanation": "Personal savings accumulated over several years.",
      "document_list": [
        { "file": "data:application/pdf;base64,JVBERi0xLjQK...", "description": "bank statement" }
      ]
    },
    {
      "requested_item_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
      "address": {
        "street_line_1": "123 Main St",
        "city": "San Francisco",
        "subdivision": "CA",
        "postal_code": "94105",
        "country": "USA"
      }
    },
    {
      "requested_item_id": "c3d4e5f6-a7b8-9012-cdef-123456789012",
      "date": "1990-06-15"
    },
    {
      "requested_item_id": "d4e5f6a7-b8c9-0123-defa-234567890123",
      "identifying_information_list": [
        { "type": "ssn", "issuing_country": "USA", "number": "123-45-6789" }
      ]
    },
    {
      "requested_item_id": "e5f6a7b8-c9d0-1234-efab-345678901234",
      "boolean": true
    },
    {
      "requested_item_id": "f6a7b8c9-d0e1-2345-fabc-456789012345",
      "text_list": ["USA", "GBR"]
    }
  ]
}

Response

A successful submission returns 201 with an empty body {}.

RFI Data Model

Field	Description
`id`	Unique identifier for the RFI.
`state`	Current state of the RFI: `on_developer`, `on_bridge`, or `closed`. See RFI Lifecycle below.
`customer_id`	The customer this RFI is associated with, if any.
`referent_id`	The id of the record this RFI is associated with, if any. This is the same id you already see in that record’s own webhook events and API responses.
`referent_type`	The type of record `referent_id` refers to: `transfer`, `drain`, `deposit`, `card_account`, or `customer` (for RFI’s raised directly on a customer, with no associated transaction). `deposit` covers both static memo activity and virtual account activity, which the Dashboard shows as a single payment type.
`additional_context`	Optional freeform text authored by Bridge ops providing extra context for the request. Present when Bridge has added a note; omitted otherwise.
`bridge_action_taken`	An action Bridge has already taken as a result of this RFI, if any: `customer_paused` or `transaction_paused`.
`expected_action_on_expiry`	The action Bridge expects to take if this RFI expires without a response: currently only `pause_customer`.
`deadline`	The date by which this RFI needs to be responded to.
`requested_items`	The items Bridge is asking for. See Requested items below.
`requested_item_groups`	Named groupings of related requested items, if any. See Requested item groups below.
`dashboard_url`	A link to view and respond to this RFI in the Bridge dashboard.
`state_changed_at`	The time the RFI’s `state` last changed.
`created_at`	Time the RFI was created.
`closed_at`	The time the RFI was closed, if it has been.

Requested items

requested_items lists the items Bridge is asking the developer to provide.

Field	Description
`id`	Unique identifier for the requested item.
`status`	The item’s resolution status: `requested` or `provided`, depending on where it is in the response workflow.
`content`	The question or request being made, in plain language.
`referent_type`	The type of record this item concerns, if any: `transfer`, `drain`, `deposit`, `card_account`, or `customer`.
`referent_id`	The id of the record this item concerns, if any.
`response_types`	The field names Bridge will accept when responding to this item.
`group_id`	The id of the requested item group this item belongs to, if any.

Requested item groups

requested_item_groups lists any named groupings of related requested items — for example, several items collected under a single “Nature of business” heading.

Field	Description
`id`	Unique identifier for the requested item group. Referenced by `group_id` on requested items belonging to it.
`name`	The group’s display name.
`description`	Additional detail about the group, if any.

RFI Lifecycle

An RFI moves through the following states:

State	Description
`on_developer`	Bridge is waiting on you or your customer to respond. This is the initial state of a newly created RFI. If Bridge needs additional information after reviewing a response, the same RFI object returns to `on_developer` with new items added to `requested_items`.
`on_bridge`	A response has been submitted and Bridge is reviewing it.
`closed`	The RFI has been resolved and no further action is needed.

RFI Webhooks

The RFI webhook is in beta and currently only covers transaction RFIs, not customer RFIs. The webhook payloads described in this section are subject to change.

Subscribe to the rfi event category on your webhook endpoint to be notified as RFI’s are created and change state. The event_object on these events matches the RFI Data Model returned by the API. If you don’t have a webhook endpoint yet, follow the webhook setup guide to create one. To add RFI events to an existing endpoint, include rfi in the event_categories array when you create or update the endpoint. See the webhooks overview and event structure docs for general webhook concepts.

Event type	Trigger
`rfi.created`	A new RFI is raised on your developer or customer account.
`rfi.updated.status_transitioned`	An existing RFI’s state changes — for example, from `on_developer` to `on_bridge` when a requested item is responded to, from `on_bridge` back to `on_developer` when Bridge requests additional information, or to `closed` when Bridge determines that the response is sufficient.
`rfi.updated`	An existing RFI changes without a state transition — for example, Bridge adds a new requested item to an RFI that’s already `on_developer`. Check `requested_items` in `event_object_changes` for the new item(s).

To check whether a RFI added/updated requested items, you can inspect event_object_changes.requested_items. It’s only present when requested_items actually changed since the last event on that RFI, so its presence alone tells you there’s something new to fetch and relay to your customer, on both rfi.updated and rfi.updated.status_transitioned events. When present, it’s a two-element array of [previous_requested_items, current_requested_items] — diff the two to find the item(s) that were added.

Example: RFI lifecycle

The following five events show a single RFI moving from on_developer to on_bridge after a response is submitted, back to on_developer when Bridge requests additional information, a new requested item being added while still on_developer, and finally to closed once Bridge finishes review.

rfi.created (on_developer)
rfi.updated.status_transitioned (on_bridge)
rfi.updated.status_transitioned (on_developer)
rfi.updated (new requested item)
rfi.updated.status_transitioned (closed)

{
  "api_version": "v0",
  "event_id": "wh_t9k2XPwmeCYAQTxRmYq7QRk",
  "event_sequence": 173,
  "event_category": "rfi",
  "event_type": "rfi.created",
  "event_object_id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
  "event_object_status": "on_developer",
  "event_object": {
    "id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
    "state": "on_developer",
    "deadline": "2026-09-16T09:00:00Z",
    "customer_id": "80b4cf5b-d4d0-4139-b8d8-de534e455cd3",
    "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
    "dashboard_url": "https://dashboard.bridge.xyz/app/support?action=view-ticket&conversationId=d9c99009-edaf-4e2f-8b4e-389173655c8a",
    "referent_type": "transfer",
    "state_changed_at": "2026-09-09T18:23:03Z",
    "bridge_action_taken": "transaction_paused",
    "expected_action_on_expiry": "pause_customer",
    "requested_items": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "status": "requested",
        "content": "What is the purpose of this payment and how will the customer be using these funds?",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      }
    ],
    "requested_item_groups": [],
    "created_at": "2026-09-09T18:23:03Z"
  },
  "event_object_changes": {},
  "event_created_at": "2026-09-09T18:23:03.694Z"
}

{
  "api_version": "v0",
  "event_id": "wh_tcRZoir1gWXYBoHMJcijjQm",
  "event_sequence": 174,
  "event_category": "rfi",
  "event_type": "rfi.updated.status_transitioned",
  "event_object_id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
  "event_object_status": "on_bridge",
  "event_object": {
    "id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
    "state": "on_bridge",
    "deadline": "2026-09-16T09:00:00Z",
    "customer_id": "80b4cf5b-d4d0-4139-b8d8-de534e455cd3",
    "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
    "dashboard_url": "https://dashboard.bridge.xyz/app/support?action=view-ticket&conversationId=d9c99009-edaf-4e2f-8b4e-389173655c8a",
    "referent_type": "transfer",
    "state_changed_at": "2026-09-09T18:23:40Z",
    "bridge_action_taken": "transaction_paused",
    "expected_action_on_expiry": "pause_customer",
    "requested_items": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "status": "requested",
        "content": "What is the purpose of this payment and how will the customer be using these funds?",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      }
    ],
    "requested_item_groups": [],
    "created_at": "2026-09-09T18:23:03Z"
  },
  "event_object_changes": {
    "state": [
      "on_developer",
      "on_bridge"
    ],
    "state_changed_at": [
      "2026-09-09T18:23:03Z",
      "2026-09-09T18:23:40Z"
    ]
  },
  "event_created_at": "2026-09-09T18:23:40.749Z"
}

{
  "api_version": "v0",
  "event_id": "wh_t4mN8kLpqRxWZvHtGsYc3Jn",
  "event_developer_id": "ffcf9216-30a2-49cd-b095-79afabf7ae6f",
  "event_sequence": 175,
  "event_category": "rfi",
  "event_type": "rfi.updated.status_transitioned",
  "event_object_id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
  "event_object_status": "on_developer",
  "event_object": {
    "id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
    "state": "on_developer",
    "deadline": "2026-09-16T09:00:00Z",
    "customer_id": "80b4cf5b-d4d0-4139-b8d8-de534e455cd3",
    "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
    "developer_id": "ffcf9216-30a2-49cd-b095-79afabf7ae6f",
    "dashboard_url": "https://dashboard.bridge.xyz/app/support?action=view-ticket&conversationId=d9c99009-edaf-4e2f-8b4e-389173655c8a",
    "referent_type": "transfer",
    "state_changed_at": "2026-09-09T18:24:00Z",
    "bridge_action_taken": "transaction_paused",
    "expected_action_on_expiry": "pause_customer",
    "requested_items": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "status": "requested",
        "content": "What is the purpose of this payment and how will the customer be using these funds?",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      }
    ],
    "requested_item_groups": [],
    "created_at": "2026-09-09T18:23:03Z"
  },
  "event_object_changes": {
    "state": [
      "on_bridge",
      "on_developer"
    ],
    "state_changed_at": [
      "2026-09-09T18:23:40Z",
      "2026-09-09T18:24:00Z"
    ]
  },
  "event_created_at": "2026-09-09T18:24:00.512Z"
}

Bridge Ops adds an additional requested item to the same RFI while it’s still on_developer. No state transition occurs, so this delivers as a plain rfi.updated event rather than rfi.updated.status_transitioned — check requested_items in event_object_changes to see the new item.

{
  "api_version": "v0",
  "event_id": "wh_t5nP9mRqsWyXbVnGvAh2Kp",
  "event_developer_id": "ffcf9216-30a2-49cd-b095-79afabf7ae6f",
  "event_sequence": 176,
  "event_category": "rfi",
  "event_type": "rfi.updated",
  "event_object_id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
  "event_object_status": "on_developer",
  "event_object": {
    "id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
    "state": "on_developer",
    "deadline": "2026-09-16T09:00:00Z",
    "customer_id": "80b4cf5b-d4d0-4139-b8d8-de534e455cd3",
    "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
    "developer_id": "ffcf9216-30a2-49cd-b095-79afabf7ae6f",
    "dashboard_url": "https://dashboard.bridge.xyz/app/support?action=view-ticket&conversationId=d9c99009-edaf-4e2f-8b4e-389173655c8a",
    "referent_type": "transfer",
    "state_changed_at": "2026-09-09T18:24:00Z",
    "bridge_action_taken": "transaction_paused",
    "expected_action_on_expiry": "pause_customer",
    "requested_items": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "status": "requested",
        "content": "What is the purpose of this payment and how will the customer be using these funds?",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      },
      {
        "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
        "status": "requested",
        "content": "What is the source of funds for this payment? Please provide supporting documentation (bank or investment statement, pay stub, invoice, receipt or contract).",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      }
    ],
    "requested_item_groups": [],
    "created_at": "2026-09-09T18:23:03Z"
  },
  "event_object_changes": {
    "requested_items": [
      [
        {
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
          "status": "requested",
          "content": "What is the purpose of this payment and how will the customer be using these funds?",
          "referent_type": "transfer",
          "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
          "response_types": ["free_text_explanation", "document_list"],
          "group_id": null
        }
      ],
      [
        {
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
          "status": "requested",
          "content": "What is the purpose of this payment and how will the customer be using these funds?",
          "referent_type": "transfer",
          "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
          "response_types": ["free_text_explanation", "document_list"],
          "group_id": null
        },
        {
          "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
          "status": "requested",
          "content": "What is the source of funds for this payment? Please provide supporting documentation (bank or investment statement, pay stub, invoice, receipt or contract).",
          "referent_type": "transfer",
          "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
          "response_types": ["free_text_explanation", "document_list"],
          "group_id": null
        }
      ]
    ]
  },
  "event_created_at": "2026-09-09T18:24:10.512Z"
}

{
  "api_version": "v0",
  "event_id": "wh_tvpV4VJ4diENPzuEc2mC81D",
  "event_developer_id": "ffcf9216-30a2-49cd-b095-79afabf7ae6f",
  "event_sequence": 177,
  "event_category": "rfi",
  "event_type": "rfi.updated.status_transitioned",
  "event_object_id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
  "event_object_status": "closed",
  "event_object": {
    "id": "8991c31c-3cf6-4128-8ad4-177fcd114c8a",
    "state": "closed",
    "deadline": "2026-09-16T09:00:00Z",
    "customer_id": "80b4cf5b-d4d0-4139-b8d8-de534e455cd3",
    "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
    "dashboard_url": "https://dashboard.bridge.xyz/app/support?action=view-ticket&conversationId=d9c99009-edaf-4e2f-8b4e-389173655c8a",
    "referent_type": "transfer",
    "state_changed_at": "2026-09-09T18:24:22Z",
    "bridge_action_taken": "transaction_paused",
    "expected_action_on_expiry": "pause_customer",
    "requested_items": [
      {
        "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
        "status": "requested",
        "content": "What is the purpose of this payment and how will the customer be using these funds?",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      },
      {
        "id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
        "status": "requested",
        "content": "What is the source of funds for this payment? Please provide supporting documentation (bank or investment statement, pay stub, invoice, receipt or contract).",
        "referent_type": "transfer",
        "referent_id": "480ba091-1be0-4669-b738-6ef4651d4f4d",
        "response_types": ["free_text_explanation", "document_list"],
        "group_id": null
      }
    ],
    "requested_item_groups": [],
    "created_at": "2026-09-09T18:23:03Z",
    "closed_at": "2026-09-09T18:24:22Z"
  },
  "event_object_changes": {
    "state": [
      "on_developer",
      "closed"
    ],
    "state_changed_at": [
      "2026-09-09T18:24:00Z",
      "2026-09-09T18:24:22Z"
    ]
  },
  "event_created_at": "2026-09-09T18:24:23.245Z"
}

Orchestration

Wallets

Issuance

Cards

Customers

Logistics

Additional information

Requests for Information (RFI's)

Overview

Customer RFI’s vs Transaction RFI’s

Responding to RFI’s

RFI API

Responding to Requested Items

Response types

Response fields

Submitting multiple kinds at once

Full example

Response

RFI Data Model

Requested items

Requested item groups

RFI Lifecycle

RFI Webhooks

Example: RFI lifecycle

​Overview

​Customer RFI’s vs Transaction RFI’s

​Responding to RFI’s

​RFI API

​Responding to Requested Items

​Response types

​Response fields

​Submitting multiple kinds at once

​Full example

​Response

​RFI Data Model

​Requested items

​Requested item groups

​RFI Lifecycle

​RFI Webhooks

​Example: RFI lifecycle

Overview

Customer RFI’s vs Transaction RFI’s

Responding to RFI’s

RFI API

Responding to Requested Items

Response types

Response fields

Submitting multiple kinds at once

Full example

Response

RFI Data Model

Requested items

Requested item groups

RFI Lifecycle

RFI Webhooks

Example: RFI lifecycle