> ## Content Index
> Fetch the complete content index at: https://stablecoininsider.org/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Create a Bridge Liquidation Address for Tempo USDC (2026)
- URL: https://stablecoininsider.org/how-to-create-a-bridge-liquidation-address-for-tempo-usdc/
- Published: 2026-09-21T06:18:04.000Z
- Updated: 2026-09-21T06:18:04.000Z
- Description: Create a Bridge Liquidation Address on Tempo for USDC: POST chain=tempo currency=usdc, point to ACH/wire or crypto, then monitor drains as deposits auto-offramp.
- Author: Alexandra
- Tags: Fintech, Stablecoins

Operators that settle Tempo USDC into fiat or another crypto rail can skip one-off transfer calls by issuing a Bridge Liquidation Address once and reusing the on-chain deposit address.

The named object is a **Bridge Liquidation Address** with **chain=tempo** and **currency=usdc**. Deposits to that permanent address auto-convert and forward to a configured fiat external account or crypto destination.

📌

Stablecoin Insider's framing: Virtual Accounts pull fiat onto Tempo. Liquidation Addresses push Tempo USDC off to fiat or crypto. Pair them when the product needs both inbound ACH/wire and outbound auto-drain.

This guide follows Bridge public docs as of September 21, 2026: [Liquidation address](https://apidocs.bridge.xyz/platform/orchestration/liquidation%5Faddress/liquidation%5Faddress), [Tempo integration guide](https://apidocs.bridge.xyz/get-started/guides/move-money/tempo-integration-guide), [Offramp with liquidation addresses](https://apidocs.bridge.xyz/get-started/guides/move-money/offramp%5Fliquidation), and [Create a Liquidation Address](https://apidocs.bridge.xyz/api-reference/liquidation-addresses/create-a-liquidation-address). It does not invent fee schedules, unsupported countries, or unpublished hostnames.

### Key Takeaways

- Create POST /v0/customers/{id}/liquidation\_addresses with chain tempo and currency usdc.
- Point the LA at an external\_account\_id (ACH/wire/SEPA) or a crypto destination\_payment\_rail plus destination\_address.
- Bridge rejects duplicate LAs for the same customer, source chain, source currency, and destination.
- Each deposit becomes a drain with states from funds\_received through payment\_processed (or returned/error).
- Named downside: KYC/jurisdiction gates, developer fees, Tempo availability, and return\_instructions must be set before production drains.

⚠️

Named downside: Liquidation Addresses require a KYC-approved customer, a valid destination (external account or crypto address), and no duplicate route for that customer. ACH drains batch daily; wire and blockchain destinations move closer to real time. Confirm Tempo USDC support and fee percent with Bridge before go-live.

## Who this is for

Use a Tempo USDC Liquidation Address when end users or treasury wallets already hold USDC on Tempo and you need automatic offramp without creating a Transfer on every deposit.

Typical buyer: remittance, neo-bank, or marketplace platforms that settled users onto Tempo via Virtual Accounts and now need the reverse rail. Bridge's Tempo guide lists Liquidation Addresses alongside wallets, transfers, issuance, and Virtual Accounts.

Stablecoin Insider already covered [how to open a Bridge Virtual Account for USDC](https://stablecoininsider.org/how-to-open-a-bridge-virtual-account-for-usdc/) and [Bridge Open Issuance for branded stablecoins](https://stablecoininsider.org/how-to-issue-a-branded-stablecoin-with-bridge-open-issuance/). This post is the operator how-to for the Liquidation Address object on the Tempo rail.

[Open Bridge Liquidation Address docs](https://apidocs.bridge.xyz/platform/orchestration/liquidation%5Faddress/liquidation%5Faddress)

## What a Liquidation Address does

Per Bridge docs, a Liquidation Address is a permanent payment route that ties a blockchain address to either a fiat external account or a crypto destination. When a customer sends USDC (or other supported currency) to that address, Bridge converts and forwards funds based on destination\_payment\_rail.

Real-time rails such as wire, SEPA, and blockchains send funds promptly. Batch rails such as ACH queue and process daily. Static template transfers are similar saved routes, but they rely on a deposit message; Liquidation Addresses give customers a unique on-chain address, which Bridge notes is more intuitive.

| Field                           | Tempo USDC LA example             | Doc source                     |
| ------------------------------- | --------------------------------- | ------------------------------ |
| chain                           | tempo                             | Tempo guide + Create LA        |
| currency                        | usdc                              | Create LA source currency enum |
| external\_account\_id           | Bank/ACH or wire destination id   | Offramp LA guide               |
| destination\_payment\_rail      | ach, wire, sepa, or a crypto rail | Create LA                      |
| destination\_currency           | usd (or eur/crypto)               | Create LA                      |
| custom\_developer\_fee\_percent | Optional override (e.g. 0.1)      | LA + Developer fees            |
| address (response)              | Permanent Tempo deposit address   | Create LA response             |

## Prerequisites before the first POST

Complete these before calling Create a Liquidation Address. Skipping any of them returns 400s or undeliverable drains.

- Bridge API key with Liquidation Address scope (sandbox key first).
- Customer created and KYC-approved for the jurisdictions you serve.
- For fiat destinations: External Account registered (API or Plaid) with currency matching destination\_currency.
- Idempotency-Key header on every create call.
- Return path configured via return\_instructions (preferred) so failed drains can be refunded on Tempo.
- Webhook endpoint for drain state changes.
- Confirmed Tempo is enabled for your developer account (Bridge Tempo guide).

Customer onboarding and external-account steps match the same Bridge stack used for [Virtual Accounts](https://stablecoininsider.org/how-to-open-a-bridge-virtual-account-for-usdc/). Reuse approved customers rather than opening a second KYC path.

## Step 1: Register the fiat or crypto destination

For ACH or wire USD offramp, create an External Account under the customer, then capture its id. Bridge's offramp guide shows US bank, SEPA IBAN, and MXN CLABE examples. The External Account currency must match destination\_currency.

For crypto-to-crypto, skip the bank object and plan destination\_payment\_rail, destination\_currency, and destination\_address instead. Tempo can also appear as a destination rail when you drain into Tempo from another chain.

💡

Stablecoin Insider's take: lock the destination before you mint the LA. Changing destinations later means Update a Liquidation Address, and duplicate create attempts for the same route fail by design.

## Step 2: Create the Tempo USDC Liquidation Address

Call **POST /v0/customers/{customerID}/liquidation\_addresses** with Api-Key and Idempotency-Key. Bridge's Tempo integration guide shows the Tempo-specific shape: currency usdc, chain tempo, external\_account\_id, destination\_payment\_rail ach, destination\_currency usd, optional destination\_ach\_reference, and optional custom\_developer\_fee\_percent.

Example fields from the Tempo guide: destination\_ach\_reference such as "test", custom\_developer\_fee\_percent "0.1". Wire destinations use destination\_wire\_message (Fedwire-style constraints). SEPA uses destination\_sepa\_reference (6–140 chars).

A successful 201 response returns id (for example la\_123), chain tempo, currency usdc, state active, and address (the permanent Tempo deposit address such as 0x…). Store address and id in your ledger; customers send Tempo USDC to address only.

| Destination type | Required create fields                                                             | Notes                             |
| ---------------- | ---------------------------------------------------------------------------------- | --------------------------------- |
| USD ACH          | external\_account\_id, destination\_payment\_rail=ach, destination\_currency=usd   | Batch daily; ACH ref max 10 chars |
| USD wire         | external\_account\_id, destination\_payment\_rail=wire, destination\_wire\_message | Near real-time per Bridge         |
| EUR SEPA         | external\_account\_id, destination\_payment\_rail=sepa, destination\_currency=eur  | SEPA reference recommended        |
| Crypto dest      | destination\_payment\_rail, destination\_currency, destination\_address            | No external\_account\_id          |

## Step 3: Fund the address and watch drains

When USDC arrives on the Liquidation Address, Bridge opens a **drain**. Retrieve history with GET /v0/customers/{customerID}/liquidation\_addresses/{liquidationAddressID}/drains, and subscribe to webhooks for state changes.

Drain states documented by Bridge include in\_review, funds\_received, payment\_submitted, payment\_processed, undeliverable, returned, refunded, error, and canceled. Forward progress only: funds\_received → payment\_submitted → payment\_processed. payment\_processed may include rail metadata such as tx\_hash, imad, or trace\_number.

Canceled often means AML review or a deposit below Bridge's minimum. Undeliverable usually means a bad destination account or unsupported asset. Wire your support runbook to those states before production volume.

## Step 4: Fees, duplicates, and updates

custom\_developer\_fee\_percent on create overrides the default Liquidation Address developer fee for that address. Values are base-100 percentages (10.2 means 10.2%). Null uses the developer default from [Developer fees](https://apidocs.bridge.xyz/platform/orchestration/fees-and-mins/devfees).

Bridge does not allow duplicate Liquidation Addresses for the same customer with the same source chain, source currency, and destination. A second create with that triple fails with an API error. To change bank or fee, use Update a Liquidation Address rather than creating a twin.

Multi-chain / multi-currency LAs (chain=evm, currency=all\_supported) exist for other products. For this how-to, keep a single-chain Tempo USDC address so operators can reason about one deposit string.

## How this fits next to Virtual Accounts and cards

Virtual Accounts move fiat onto Tempo USDC. Liquidation Addresses move Tempo USDC out. Together they form a closed loop for payment apps building on Tempo with Bridge wallets and transfers.

If the product also needs local card spend against a USDC wallet, compare [BVNK USDC Cards](https://stablecoininsider.org/how-to-issue-a-bvnk-usdc-card/) and Circle-style [stablecoin payouts](https://stablecoininsider.org/how-to-send-a-circle-stablecoin-payout/). For generic USDC ACH/wire without Tempo, see [how to off-ramp USDC to ACH or wire](https://stablecoininsider.org/how-to-off-ramp-usdc-to-ach-or-wire/).

[How to Open a Bridge Virtual Account for USDCOperator how-to for Bridge Virtual Accounts that settle fiat deposits to USDC, the inbound counterpart to Liquidation Addresses.![](https://stablecoininsider.org/favicon.ico)Stablecoin Insider](https://stablecoininsider.org/how-to-open-a-bridge-virtual-account-for-usdc/)

## Operator checklist before go-live

- Sandbox: create External Account → create Tempo USDC LA → deposit test USDC → observe drain to payment\_processed.
- Assert Idempotency-Key reuse returns the same LA, and a true duplicate destination fails.
- Set return\_instructions on Tempo so failed fiat payouts can reverse on-chain.
- Map webhook drain states into your ledger and support SLAs (especially ACH batch lag).
- Confirm custom\_developer\_fee\_percent with finance; document it in customer pricing.
- Store the returned address immutably; never regenerate for the same route.

Need the primary reference? Start with Bridge's Tempo Liquidation Address example, then wire External Accounts and drain webhooks before the first production deposit.

[Read Tempo integration guide ](https://apidocs.bridge.xyz/get-started/guides/move-money/tempo-integration-guide) 

## Security and compliance notes for operators

Travel Rule data can be attached on create when the same originator or beneficiary applies to every future drain. If counterparties vary per deposit, submit Travel Rule payloads per movement instead.

Because destinations are permanent routes, treat LA addresses like bank account numbers: scope them per customer, rotate only via Update, and monitor for unexpected deposit\_tx\_hash activity on the drain history endpoint.

## FAQ

#### What is a Bridge Liquidation Address?

A permanent blockchain address that auto-routes incoming crypto (such as Tempo USDC) to a configured fiat external account or crypto destination without a new Transfer API call per deposit.

#### How do you create a Tempo USDC Liquidation Address?

POST /v0/customers/{customerID}/liquidation\_addresses with currency usdc, chain tempo, Idempotency-Key, and either an external\_account\_id plus fiat rail fields or a crypto destination\_payment\_rail and destination\_address.

#### Can you create two Liquidation Addresses for the same destination?

No. Bridge rejects duplicates for the same customer, source chain, source currency, and destination. Update the existing LA instead.

#### How fast do ACH vs wire drains settle?

Bridge documents batch rails such as ACH as queued and processed daily, and real-time rails such as wire, SEPA, and blockchains as sending promptly after conversion.

#### What is a drain?

A drain is the lifecycle record for one deposit that Bridge converts and forwards from a Liquidation Address. Track states via drain history and webhooks until payment\_processed or a failure state.

#### Do Virtual Accounts replace Liquidation Addresses?

No. Virtual Accounts onramp fiat to Tempo USDC. Liquidation Addresses offramp Tempo USDC to fiat or crypto. Most Tempo payment apps need both.

---

This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.