How to Create a Tempo USDC Liquidation Address on Bridge

Bridge operators can create a permanent Tempo USDC Liquidation Address by POSTing to /v0/customers/{customerID}/liquidation_addresses with chain=tempo and currency=usdc. The API returns a permanent Tempo deposit address and an id; funds sent to that address are converted and forwarded to a registered fiat external account or a crypto destination.

Prerequisites include a Bridge API key with Liquidation Address scope, a customer approved for KYC in supported jurisdictions, and a destination already registered. For fiat destinations, an External Account must be created with matching currency. For crypto destinations, provide destination_payment_rail and destination_address. Calls must include an Idempotency-Key header. Operators should configure return_instructions and a webhook endpoint before processing production volume and test the flow in sandbox first.

The create call requires chain=tempo and currency=usdc and either an external_account_id plus rail-specific fields for ACH, wire or SEPA, or destination_payment_rail and destination_address for crypto. Optional fields include custom_developer_fee_percent and rail reference fields such as destination_ach_reference, destination_wire_message or destination_sepa_reference. A successful 201 response returns the Liquidation Address id and the permanent on-chain address; operators must store both in their ledger because customers will send USDC to that single address.

When USDC arrives at the Liquidation Address, Bridge opens a drain record for that deposit. Drains move through states such as in_review, funds_received, payment_submitted and payment_processed. Failure states include undeliverable, returned, refunded, error and canceled. Entries marked payment_processed often include rail metadata such as tx_hash or trace numbers. ACH drains are batched and processed daily; wire, SEPA and blockchain destinations process closer to real time. Operators should map webhook events into their ledger and prepare operational runbooks for each drain state and for ACH batching delays.

Bridge rejects attempts to create duplicate Liquidation Addresses for the same customer with the same source chain, source currency and destination. To change a destination or fee for an existing route, use Update a Liquidation Address. The custom_developer_fee_percent field on create overrides the developer default and is expressed as a base-100 percentage; null falls back to the account default.

Security and compliance requirements include a KYC-approved customer and a valid destination. Set return_instructions on Tempo so failed fiat payouts can be reversed on-chain. Travel Rule data may be attached at creation when the same originator or beneficiary applies to all future drains; otherwise include travel rule payloads with individual movements. Treat Liquidation Addresses like bank account numbers: scope them per customer, rotate them via Update and monitor deposit_tx_hash activity through the drain history endpoint.

Typical users of Tempo USDC Liquidation Addresses are remittance firms, neo-banks and marketplaces that already settle users onto Tempo via Virtual Accounts and require an automated outward rail. Before production, test idempotency behavior in sandbox, validate return flows, confirm Tempo USDC support and fee rates with Bridge, and document developer fees in customer pricing.