Static Memos are long-lived deposit instructions that accept fiat funds through wire and ACH push and send funds to the configured destination wallet. The same Static Memo can receive both wires and ACH pushes interchangeably.
Don’t forget thedeposit_message !For Static Memos, it is very important that the customer includes the deposit_message when they send funds. Failure to include the deposit_message will result in a significant delay in processing or a return of the funds.
For memo-based blockchains such as Stellar, you may include an optional blockchain_memo in the destination field. Bridge will forward the memo when sending crypto funds.
Update the destination details for an existing Static Memo. Future transactions will use the updated destination details. All fields in this request are optional. Updating a Static Memo will also create an account_update event in the history for that account.
Request
Copy
Ask AI
curl --location --request PUT 'https://api.bridge.xyz/v0/customers/cust_alice/static_memos/sm_123' \ --header 'Content-Type: application/json' \ --header 'Api-Key: <Api-Key>' \ --data-raw '{ "destination": { "payment_rail": "ethereum", "currency": "usdt", "address": "0xDEADBEEF" }, "developer_fee_percent": "2.5", // 2.5%, omitting will not change the existing dev fee percent }'
This endpoint provide a history of activity for Static Memos such incoming fiat funds received and outgoing payments on chain. See List History of Static Memo activity for more information about the types of events returned from these endpoints.
Bridge has received funds and is preparing to move them on the customer’s behalf.
payment_submitted
Bridge has sent the payment and is awaiting confirmation (usually takes a few minutes on-chain).
payment_processed
Funds have arrived at the destination. Final state.
in_review
Temporary review state. Bridge may reach out for additional info.
refund
Bridge couldn’t complete the transfer and is returning funds to the sender.
account_update
Triggered when a Virtual Account’s destination details (e.g. address, currency) are updated.
Please note that a transaction will always progress from funds_received → payment_submitted → payment_processed. It can never go backwards.All transaction-triggered events include a deposit_id field. This id is unique for each transaction that Bridge receives through this Static Memo and can be used to link separate events to the same source transaction.
Static memos do not support microdeposit or challenge deposit verifications.
Information about a fiat deposit received. The funds_received event amount always matches the full amount that the customer sent before any fees are deducted. We also provide any source information we have about the sender of a deposit. The information available differs by source payment rail:
ACH: description, payment rail
Wire: beneficiary name, routing number, bank name, IMAD, OMAD (deprecated), payment rail
Information about any funds sent on chain using the deposit instructions. This event is created when the funds are sent on chain. The payment_submitted event amount is the funds sent to the destination after all fees are taken out and includes a breakdown of the amount of each customer-facing fee. Some information such as destination_tx_hash may not be available immediately after the payment_submitted event is created but will be populated later when the transaction is confirmed on chain.For convenience, the source deposit information is included in this event as well if available.
Information about any funds sent on chain using the deposit instructions. This event is created when the funds are confirmed on chain. The payment_processed event amount is the funds sent to the destination after all fees are taken out and includes a breakdown of the amount of each fee. Thedestination_tx_hashwill always be populated for these events. This is final event in the onramp payment lifecycle and the best event to determine when a payment is fully complete.For convenience, the source deposit information is included in this event as well if available.
This event happens when a transaction enters the manual review queue. Bridge may reach out to obtain more information about the transaction before processing.
Copy
Ask AI
{ "id": "sm_event_363", "customer_id": "cust_alice", "static_memo_id": "sm_123", "type": "in_review", "amount": "120.0", "currency": "usd", "developer_fee_amount": "1.25", "exchange_fee_amount": "2.2", "subtotal_amount": "120.0", "gas_fee": "0.0", "created_at": "2020-01-01T00:00:00.000Z", "deposit_id": "deposit_123", "source": { "payment_rail": "ach_push", "description": "ACH description", "sender_name": "The name of the business or individual who sent the ACH", "sender_bank_routing_number": "The routing number of the entity who sent this ACH transaction" }}
Account update
If a Static Memo is modified using the Update a Static Memo endpoint, its history will include an account_update event to track what changed. The account_updates field in this event will contain a map of fields with their previous and updated values.
