1. 🚀 Features
Pix2DePix API
  • 📜 API Overview
  • Docs
    • 🔑 Authentication
    • 💻 Examples
    • 🪝 Webhook
    • ✅ Possible Statuses
      • 📥💰 Deposit Statuses
      • 📤💸 Withdraw Statuses
    • 🛡️ Security & Limits
      • ✅ Best Practices
      • 🪲 Bug Bounty
      • 🧱 Firewall
      • 🚦 API Limits
    • 🧩 Advanced (optional)
      • 🎲 Nonce
      • 🔀 Sync / Async call
    • 🚀 Features
      • ⏱️ QR Delay
      • 💬 Pix Messaging
      • 🔐 Pix2FA
  • API Endpoints
    • Ping
      GET
    • Deposit (PIX ➔ DePix)
      POST
    • Deposit Status
      GET
    • Deposits
      GET
    • User Info
      GET
    • Pix2FA
      POST
    • Withdraw
      POST
    • Withdraw Status
      GET
  • Schemas
    • AsyncResponse
    • AllPossibleObjResponses
    • StandardResponse
    • PingObjOrError
    • JWTClaims
    • ObjResponse
    • ErrorObj
    • PingObj
    • ErrorResponse
    • DepositRequest
    • DepositObjOrError
    • DepositObj
    • PingResponse
    • DepositResponse
    • DepositStatusObj
    • DepositStatusResponse
    • DepositWebhookBody
    • DepositsResponse
    • DepositStatus
    • UserInfoResponse
    • Pix2FAResponse
    • WithdrawStatusResponse
    • WithdrawStatusObj
    • WithdrawResponse
    • WithdrawObj
    • WithdrawStatus
    • WithdrawWebhookBody
    • MEDWebhookBody
  1. 🚀 Features

⏱️ QR Delay

This feature allows you to delay the conversion of a Pix deposit into DePix after the payment is completed.
Instead of processing the deposit immediately, the system will wait for the defined period on your request (parameter delayDepixInHours) before executing the conversion.

Use Cases#

Fraud prevention / risk analysis window
Controlling MED (Mecanismo Especial de Devolução) exposure in merchant payments

How it works#

Create a deposit using the standard /deposit endpoint.
Include the delayDepixInHours parameter in your request.
The value represents the delay (in hours) before the Pix payment is converted into DePix.
The Pix QR code is generated and can be paid normally by the end user.
After the payment is confirmed, the system will wait the specified time before processing the conversion.
The deposit will remain in the delayed status until processing (see Possible Statuses)
After the delay, the system converts the funds into DePix and completes the deposit.

Considerations#

The delay only affects the conversion to DePix, not the Pix payment itself.
Once the delay is configured, it cannot be changed after QR generation.
The deposit will only be finalized after the delay period has fully elapsed.
Ensure your application logic accounts for the delayed settlement state when querying /deposit-status.

Example#

Below is an example of creating a deposit with a delay of 48 hours for sending the DePix.
Deposit request (for more details, please refer to Deposit endpoint)
{
  "amountInCents": 100,
  "delayDepixInHours": 48
}
Modified at 2026-03-25 12:52:54
Previous
🔀 Sync / Async call
Next
💬 Pix Messaging
Built with