STABLECOIN INFRASTRUCTURE FOR DEVELOPERS

Convert USDT to BRL via Pix by API

Build a USDT-funded Pix payout flow for your product. Documented examples use USDT on Polygon or Tron; confirm support for your account and operation before sending.

USDTUSDT
USDCUSDC
PixPix

How USDT to BRL payouts work

The off-ramp uses a supported USDT balance to fund a BRL Pix payment. Production requires verification and permission for the flow. The recipient and quote need confirmation before the wallet signs the payout.

  1. 1Select the source wallet and obtain its protected key through POST /api/wallet/keys, following wallet PIN and subaccount scope requirements.
  2. 2Confirm the beneficiary through POST /api/wallet/payout/beneficiary. Review the fee, BRL payment amount and total debit in the linked quote.
  3. 3Authorize POST /api/wallet/payout with the required wallet credentials. When executing with quoteId, use the linked quote’s conditions.
  4. 4Persist transactionId, check GET /api/wallet/payout/{transactionId}, verify webhook signatures and reconcile the final state before marking the payment complete.

USDT to BRL fees and quotes

API payouts have their own pricing, which can vary by account, asset, network and enabled flow. Check the fee and total debit in the beneficiary-linked quote. When executed with quoteId, the payout uses that quote’s conditions. The commercial schedule below applies only to operations covered by a proposal or contract adopting it; its BRL 0.75 minimum does not automatically apply to API payouts.

Monthly volume (BRL)Commercial service fee
Up to 100,0002.00%
Above 100,000 to 300,0001.60%
Above 300,000 to 800,0001.25%
Above 800,000 to 2 million0.95%
Above 2 million to 5 million0.70%
Above 5 million0.50%

USDT networks for Pix payouts

Documented payout examples use USDT on Polygon or Tron. The wider platform asset list is not a guarantee of support for this payout flow. Confirm your account’s enabled asset and network, and use its quote instead of assuming a fixed exchange rate.

Sandbox quickstart: request a quote

Create a separate account at app-sandbox.hodle.com.br and issue a test key. Set HODLE_SANDBOX_API_KEY on your backend, then run this curl request for BRL 100 into USDC via Base. A quote is indicative: it does not execute a payment or lock a rate. Supported sandbox operations use Base Sepolia test tokens and simulate Pix; sandbox rates are not production prices. This shared quote example tests BRL to USDC; it does not execute a USDT-to-BRL payout. Follow the sandbox coverage guide when testing the payout flow.

cURL · sandbox quote · no payment executionbash
curl --request POST \
  --url https://sandbox-api.hodle.com.br/api/quote \
  --header "Authorization: Bearer $HODLE_SANDBOX_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "inputCurrency": "BRL",
    "inputPaymentMethod": "PIX",
    "outputCurrency": "USDC",
    "outputPaymentMethod": "BASE",
    "inputAmount": "100.00"
  }'

Frequently asked questions

Practical questions before integrating.

Can I convert USDT to BRL via Pix by API?

Yes. Hodle supports stablecoin-funded Pix payouts, with documented USDT examples on Polygon or Tron. Your account must have the required verification and flow permissions.

How much does a USDT to BRL payout cost?

API payout pricing can vary by account, asset, network and enabled flow. Check the fee and total debit in the beneficiary-linked quote. The commercial volume schedule and its minimum do not automatically apply to this endpoint.

Is the exchange rate fixed by the quote example?

No. POST /api/quote is indicative and does not lock a rate or execute a payment. Review the beneficiary-linked payout quote before authorization; execution with quoteId uses that quote’s conditions.

Can I test without sending real Pix payments?

Yes. Use a separate sandbox registration and test key. Supported operations use Base Sepolia test tokens and simulate Pix; check the sandbox guide for flow coverage. Production assets and permissions are separate.

How do I know the Pix payout has completed?

Keep the transactionId, check the payout status and verify webhook signatures. Deduplicate events and wait for the expected final state. Request acceptance or a timeout alone does not establish the payment outcome.

Ready to integrate?

Test with a separate sandbox account before applying for production verification and flow permissions.