1
Sender
Done once per sender. Reused in every remittance.
- Onboarding — MSB registers its customer: identification, address, documents.
- Compliance — LB Pay assigns a compliance level (
LEVEL_0toLEVEL_3) and limits per window.LEVEL_0cannot send.
2
Price and send
For each remittance.
- Quote — MSB requests a price for a fixed USD or BRL amount. One price, short validity. Not linked to a sender.
- Beneficiary — Choose an existing beneficiary or register a new one with a Pix key. Before or after the quote; required for the withdrawal.
- Withdrawal and funding — MSB creates the withdrawal with the quote, sender, beneficiary, Pix key, purpose, relationship and funding mode. LB Pay validates, reserves credit or balance and creates the remittance.
3
Execute and settle
Run by LB Pay.
- FX and funding — FX contracted.
PREFUNDED: USD debited from the MSB’s balance in the US.CREDIT: BRL advanced.INVENTORY: volume used from the lot, at the lot rate. - Pix and receipt — LB Pay confirms the Pix key belongs to the beneficiary and credits the BRL. Receipt and notification issued.
- Settlement — For
CREDIT, the MSB pays the settlement by the due date.
USDC Inventory. Instead of one quote per remittance, the MSB can contract FX volume in advance: request a quote with
usage = INVENTORY and create an Inventory Lot with POST /v1/inventories. Each withdrawal then uses funding.mode = INVENTORY, the inventoryId, the BRL amount and senderQuote, with no quoteId. Rate and amounts come from the lot. See USDC Inventory.A quote can be requested without a sender or a beneficiary. A withdrawal can only be created with an eligible sender, an active, approved beneficiary and a valid Pix key. Because the sender is only checked at the withdrawal, check the sender’s status and limits before showing the price to your customer. If registering the beneficiary takes longer than the quote validity, request a new quote.