Skip to main content
Bridge works with various banking partners and financial institutions to realize our Orchestration services. On occasion, these institutions may reach out to Bridge to notify us that a fiat deposit into that financial institution was later recalled by the sender, and for Bridge to return the funds to the sender if possible. Bridge calls these funds requests. Many, but not all, funds requests, are due to fraud or suspected fraud. Bridge provides a booleanfraud field in our funds request responses to denote whether funds were recalled due to fraud or non-fraudulent reasons. Funds requests are tied to deposits, and a deposit_id will be provided in the API response. This deposit_id can be cross-referenced in the virtual account event history to determine which customer’s deposit is being referenced. In general, Bridge will attempt to return the funds if the money movement has not yet completed and funds have not left Bridge for the recipient. Our Operations team will also follow up with developers for all fraudulent funds requests. We may also take remediary action if the number of funds requests exceeds levels deemed acceptable to Bridge.

​
List All Funds Requests

Request
curl --request GET \
     --url 'https://api.bridge.xyz/v0/funds_requests' \
     --header 'Api-Key: <Api-Key>' \
     --header 'accept: application/json'

​
List All Funds Requests with Filters

Request
curl --request GET \
     --url 'https://api.bridge.xyz/v0/funds_requests?customer_id=123&fraud=true' \
     --header 'Api-Key: <Api-Key>' \
     --header 'accept: application/json'