curl --request GET \
--url https://api.bridge.xyz/v0/customers/{customerID}/transfers \
--header 'Api-Key: <api-key>'{
"count": 2,
"data": [
{
"$ref": "#/components/examples/AchOnrampFundsReceivedTransferResponse/value"
},
{
"$ref": "#/components/examples/AchOfframpTransferResponse/value"
}
]
}Get all active and completed transfers for a customer.
curl --request GET \
--url https://api.bridge.xyz/v0/customers/{customerID}/transfers \
--header 'Api-Key: <api-key>'{
"count": 2,
"data": [
{
"$ref": "#/components/examples/AchOnrampFundsReceivedTransferResponse/value"
},
{
"$ref": "#/components/examples/AchOfframpTransferResponse/value"
}
]
}A UUID that uniquely identifies a resource
1 - 42The number of items to return (default of 10, max of 100)
This is a transfer id. If this is specified, the next page that starts with a transfer right AFTER the specified transfer id on the transfer timeline, which is always ordered from the newest to the oldest by creation time, will be returned. This also implies that transfers older than the specified transfer id will be returned (shouldn't be set if ending_before is set)
This is a transfer id. If this is specified, the previous page that ends with a transfer right BEFORE the specified transfer id on the transfer timeline, which is always ordered from the newest to the oldest by creation time, will be returned. This also implies that transfers newer than the specified transfer id will be returned (shouldn't be set if starting_after is set)
The hash of the transaction
This is a unix timestamp in milliseconds. If this is specified, objects updated AFTER the specified timestamp will be returned
This is a unix timestamp in milliseconds. If this is specified, objects updated BEFORE the specified timestamp will be returned
Filter transfers by their external state. See Transfer States for more details.
awaiting_funds, funds_received, payment_submitted, payment_processed, in_review, kyc_required, kyc_in_review, developer_kyb_required, canceled, error, returned, refunded, undeliverable List of transfers (the returned list is empty if none found)
The number of transfers returned
Show child attributes
A UUID that uniquely identifies a resource
1 - 42Amount of the transfer, expressed as a decimal string. Examples include "100.25", "0.1", "1.234567", "1.01" etc.
It is denominated in the source currency if that is a fiat currency, or in the fiat currency to which the source currency is pegged.
Fiat currency for the transfer amount and developer fee. It's the source currency if that is a fiat currency or the fiat currency to which the source currency is pegged.
usd, eur, mxn The id of the Bridge customer that you are moving funds on behalf of.
The fee, expressed as a decimal string, represents the amount you wish to reserve for your own account. This fee is the final amount deducted from what your customer ultimately receives, rather than a percentage.
It is denominated in the source currency if that is a fiat currency, or in the fiat currency to which the source currency is pegged.
The source of the transfer, which could be an external bank account, a bridge account, or a crypto wallet address
Show child attributes
When eur is specified as the source currency:
sepa;usdc or eurc are supported as the destination currency
The source currencydai, eur, eurc, mxn, pyusd, usd, usdb, usdc, usdt When sepa is specified as the source rail:
eur;usdc or eurc are supported as the destination currency
The source payment railach, wire, ach_push, ach_same_day, arbitrum, avalanche_c_chain, base, bridge_wallet, ethereum, optimism, polygon, sepa, solana, spei, stellar, swift, tron (SEPA only) The payment scheme used for this transaction, such as SEPA Credit Transfer or SEPA Instant
reversed_payment, sepa_credit, sepa_instant A UUID that uniquely identifies a resource
1 - 42(Wire only) The OMAD of a wire transfer, if available
1 - 40(Wire only) The IMAD of a wire transfer, if available
1 - 40(Wire only) The name of the beneficiary of the bank account that the customer sent the deposit to
(Wire only) The address of the beneficiary of the bank account that the customer sent the deposit to
(Wire only) The routing number of the bank that the customer sent the deposit to
(Wire only) The name of the bank that the customer sent the deposit to
(Wire only) The originator name of this wire
(Wire only) The originator address of this wire
(Wire only) The memo for this wire
(Bridge Wallet only) The ID of the Bridge Wallet to draw funds from
1 - 42(ACH only) The name of the business or individual who initiated the transaction
(ACH only) The routing number of the entity that initiated this ACH transaction
(ACH only) The description of the deposit that the customer sent
The clave de rastreo or tracking number of a SPEI transaction
1 - 30The unique transaction identifier for a Pix transaction
1 - 50The crypto wallet address that the customer will send funds from, in order to kick off this transfer
The destination of the transfer, which could be an external bank account, a bridge account, or a crypto wallet address
Show child attributes
When eur is specified as the destination currency, the destination rail must be sepa.
The destination currency
dai, eur, eurc, mxn, pyusd, usd, usdb, usdc, usdt When sepa is specified as the destination payment rail, the destination currency must be eur; when swift is specified as the destination payment rail, the destination currency must be usd.
The destination payment rail
ach, wire, ach_push, ach_same_day, arbitrum, avalanche_c_chain, base, ethereum, fiat_deposit_return, optimism, polygon, sepa, solana, spei, stellar, swift, tron External bank account Bridge should send the funds to. The currency associated with the External Account must match the destination currency.
1 - 42The Bridge Wallet to which Bridge will send the funds. The chain associated with the Bridge Wallet must match the destination payment rail.
1 - 42(Wire only) The OMAD of a wire transfer, if available
1 - 40(Wire only) The IMAD of a wire transfer, if available
1 - 40The trace number of an ACH transfer
15A message to be sent with a wire transfer. It can have up to 140 characters. This message will be validated against 4 lines, each with a max length of 35 characters according to the Fedwire standard. A message to be sent with a wire transfer, only allowed when the payment rail is a wire. This message will be validated against 4 lines, each with a max length of 35 char according to the Fedwire standard.
1 - 256A reference message to be sent with a SEPA transaction. We recommend you set a unique value to help you and your customers track payments end to end. It must be from 6 to 140 characters. The allowed characters are a-z, A-Z, 0-9, spaces, ampersand (&), hyphen (-), full stop (.), and solidus (/). If not populated, the default value is "Payment via Bridge {unique_token}".
6 - 140A payment reference message or remittance information to be included in a SWIFT transaction. It can have at most 4 lines (separated by "\n"), each line with a max length of 35 chars. The allowed characters are a-z, A-Z, 0-9, special characters (/ - ? : ( ) . , ' +), and space
1 - 190A payment reference message or remittance information to be included in a SPEI transaction. The allowed characters are alphanumeric a-z, A-Z, 0-9, and space
1 - 40A payment reference message for newer payment rails (e.g. Pix).
Which party will bear the charges for the SWIFT transaction. When left blank, sha will be used as the default.
our, sha A reference message to be sent with an ACH transaction. It can be at most 10 characters, A-Z, a-z, 0-9, and spaces.
1 - 10The UETR of this SEPA transaction, for tracing purposes.
36The memo to include when sending funds on chain. Only allowed for blockchains that support memos such as Stellar A message to be sent with a crypto transaction, only allowed when the payment rail is Stellar.
A UUID that uniquely identifies a deposit
1 - 42The clave de rastreo or tracking number of a SPEI transaction
1 - 30The unique transaction identifier for a Pix transaction
1 - 50The name of the institution sending the funds
The crypto wallet address that the customer wishes to ultimately receive funds at, in order to complete this transfer
Status of the transfer. See Transfer States for more details.
awaiting_funds, in_review, funds_received, payment_submitted, payment_processed, canceled, undeliverable, returned, refunded Receipt information of a transfer
Show child attributes
The initial amount of the transfer, represented as a decimal string. Examples include "100.25", "0.1", "1.234567", "1.01" etc.
It's denominated in the transfer's fiat currency (see the top-level currency field for more info)
The fee, expressed as a decimal string, represents the amount you wish to reserve for your own account. This fee is the final amount deducted from what your customer ultimately receives, rather than a percentage.
It is denominated in the transfer's fiat currency (see the top-level currency field for more info).
The fee, expressed as a decimal string, represents the amount Bridge charges for facilitating the transfer. This is the final amount to take out of what is ultimately received by your customer, not a percentage.
It's denominated in the transfer's fiat currency (see top-level currency field for more info).
The initial amount of the transfer less fixed fees (including the developer_fee and exchange_fee). Examples include "100.25", "0.1", "1.234567", "1.01" etc.
It's denominated in the transfer's fiat currency (see top-level currency field for more info).
For Prefunded Accounts, this value will represent the remaining account balance after the transfer.
The fee, expressed as a decimal string. It's deducted from the withdrawn amount to pay for gas. Only nonzero to crypto withdrawals that cost gas (e.g. USDT or DAI), and only known when the transaction is confirmed on-chain. Will be missing if not yet known.
It's denominated in the fiat currency to which the destination currency is pegged.
The final amount of the transfer, expressed as a decimal string, equal to the subtotal_amount minus any gas fees. If the gas fee is not known, this field will be missing. Examples include "100.25", "0.1", "1.234567", "1.01" etc.
It's denominated in the destination currency if that is a fiat currency or the fiat currency to which the destination currency is pegged.
The hash of the on-chain deposit to the source address, where applicable
The hash of the on-chain transfer to the destination address, where applicable
The effective exchange rate can be calculated by dividing the converted amount by the amount available for conversion after deducting the developer fee. This rate includes a currency conversion spread and is subject to a rounding precision loss during the calculation. Currently it's populated for SEPA onramp/offramp transfers only.
The URL of a user-facing copy of the receipt.
Time of creation of the transfer
Time of update of the transfer
A client-provided reference ID that uniquely identifies a resource in the client's system
1 - 256The fee percent, expressed as a decimal string from 0.0 to 100.0, represents the percentage of the transfer you wish to reserve for your own account.
This field must be set instead of developer_fee when using Flexible Amounts.
Some transfers require a deposit to be made by the customer before Bridge can start the process. Instructions for how to kick off the transfer will be included here. The deposit must match these instructions exactly, or the transfer will fail.
Show child attributes
The payment rail that Bridge is expecting funds to arrive on. For a crypto based source on the transfer, this is the chain, i.e. ethereum or polygon The source payment rail
ach, wire, ach_push, ach_same_day, arbitrum, avalanche_c_chain, base, ethereum, optimism, polygon, solana, spei, stellar Amount of the deposit, represented as a dollar denominated string. Examples include "100.25", "0.1", "1.234567", "1.01" etc. Amount of the deposit, expressed as a decimal string. It's denominated in the source currency if that is a fiat currency, or in the fiat currency to which the source currency is pegged. Examples include "100.25", "0.1", "1.234567", "1.01" etc.
The source currency
dai, pyusd, usd, usdb, usdc, usdt The crypto wallet address that the customer will send funds from, in order to kick off this transfer
The crypto wallet address the customer will send funds to in order to initiate the payment processing
The message that the customer MUST include in their wire memo/message or ach push description
The message that the customer MUST include in their wire memo/message, ach push description, or sepa reference.
The name of the bank that the customer should send the deposit to
The address of the bank that the customer should send the deposit to. For SEPA, the country in this address should be used for sending the deposit
The routing number of the bank that the customer should send the deposit to
The account number of the bank that the customer should send the deposit to
The name of the beneficiary of the bank account that the customer should send the deposit to
The address of the beneficiary of the bank account that the customer should send the deposit to
For SEPA, the International Bank Account Number (IBAN) that the customer should use to send the deposit
For SEPA, the Bank Identifier Code (BIC) that the customer should use to send the deposit
For SPEI, the CLABE (account number) that the customer should use to send the deposit
For SEPA, the name of the bank account holder that the customer should use to send the deposit
If present, the message that the customer MUST include in their on chain transfer. Only used for memo-based blockchains such as Stellar and Tron
Return information, if the transfer has been returned.
Was this page helpful?