Receiving the payment

After accept, BlendFi watches the Pix payment. Pix is atomic at the provider: either the end customer pays the exact amount within the window, or the payment is not confirmed.

The two paths

1. Paid within the window → funded → automatic settlement

The happy path. The end customer pays the Pix QR before deposit_window_expires_at. BlendFi receives provider confirmation, the conversion transitions to funded, on-chain settlement advances automatically, and the conversion ends in completed. You receive conversion.completed.

You do not need to call anything. Settlement is fully automatic from funded onward.

2. Window expired with no payment → expired

If the window passes with no confirmed payment, the conversion transitions to expired (terminal), the limit reservation is released, the lock is cleared. There is no payment to handle.

Why onramp has no standby

Unlike offramp, Pix is atomic at the provider. There is no "partial Pix" or "Pix with wrong amount": either the payment exactly matches the quoted amount or it is not confirmed. This eliminates the under_funded and over_funded cases that exist in offramp.

Webhooks you receive

The full webhook semantics live in the Webhooks section.

Typical total time

From accept to conversion.completed, the happy path is typically:

• 0 to 15 min: end customer pays the Pix QR.
• ~10s after payment: Pix provider confirms.
• Seconds to minutes: on-chain settlement confirms.
• conversion.completed fires.

See USDT in the glossary for details on on-chain confirmation timing.

Next step

• Cancellation: how to exit before payment arrives.