Skip to main content
Use this procedure when RGB USDT is the source asset. The invoice locks the RGB allocation at a Bitcoin HTLC output. Use an RGB wallet that can pay a witness invoice, post the consignment, and broadcast the transfer. See RGB concepts and the RGB Lightning Node quick start.

Fund the intent

  1. Request a quote with the RGB asset identifier as source_token.
  2. Create the intent with the user’s Bitcoin address and user_source_public_key.
  3. Check that approval_mechanism is broadcast.
  4. Read deposit_tx_data.RgbLock.witness_invoice.
  5. Pay the invoice from the user’s RGB wallet. Post the consignment and broadcast the wallet’s colored transaction.
  6. Submit the broadcast transaction hash to POST /affiliate/v1/intents/{intent_id}/deposit.
  7. Track the intent status.
The intent response includes these fields:
The invoice contains the asset, amount, and lock destination. The user’s wallet creates the colored transaction. Do not sign the resolver’s template PSBT or submit a psbt approval for this flow. The deposit check validates both the on-chain lock and the RGB consignment. Error code 76 with HTTP 409 permits a retry with the same transaction hash. See Report a user deposit. For lock templates and claims, see RGB USDT settlement.