Initiate a Pix to stablecoin transaction

Every transaction requires an auth challenge before a Pix QR code is issued. The challenge type depends on the client’s riskTier from KYC.

Risk Tier	Auth Challenge
`STANDARD`	TOTP MFA (`MFA_TOTP`)
`HIGH` / `PEP`	Liveness verification (`LIVENESS`)

Request

string

required

Your LaaS API key.

string

required

Token from POST /v1/laas/kyc/submit. Must not be expired.

number

required

Amount in BRL (R$). Minimum: 50. Maximum: 50000 per transaction.

string

required

Stablecoin to receive: "USDT" or "USDC".

string

required

EVM-compatible wallet address (EIP-55 checksum). Polygon network.

Request

{
  "kycToken": "kyc_1719000000_abc123",
  "amountBrl": 500,
  "asset": "USDT",
  "walletAddress": "0xYourUserWalletAddress"
}

Response

Standard Risk
High Risk / PEP

string

Transaction ID. Use in confirm-mfa and status calls.

string

PENDING_AUTH

string

MFA_TOTP

string

Human-readable instruction to display to your user.

{
  "success": true,
  "data": {
    "transactionId": "tx_1719000000_xyz",
    "status": "PENDING_AUTH",
    "authChallenge": {
      "type": "MFA_TOTP",
      "instruction": "Request the 6-digit TOTP code from your user"
    }
  }
}

string

LIVENESS

string

URL to redirect the user to for liveness verification. Valid for 10 minutes.

{
  "success": true,
  "data": {
    "transactionId": "tx_1719000000_xyz",
    "status": "PENDING_AUTH",
    "authChallenge": {
      "type": "LIVENESS",
      "instruction": "User must complete liveness verification",
      "livenessUrl": "https://partners.mippo.io/liveness/tx_1719000000_xyz"
    }
  }
}

When liveness passes, Mippo fires a transaction.pix_ready webhook with the pixPayload. You do not need to poll.

Overview

KYC

Transactions

Partner

Initiate a Pix to stablecoin transaction

Request

Response

​Request

​Response

Request

Response