Confirm MFA for a pending transaction

Used only when authChallenge.type === 'MFA_TOTP'. On success, returns the Pix QR payload to display to your user.

Request

string

required

Your LaaS API key.

string

required

Transaction ID from POST /v1/laas/transactions/initiate.

string

required

6-digit TOTP code from the user’s authenticator app.

Request

{
  "totpCode": "482910"
}

Response

string

Transaction ID.

string

PENDING_PAYMENT — Pix is ready, waiting for user to pay.

string

Pix Copia e Cola string. Encode as a QR code and display to the user.

string

ISO 8601 timestamp when the Pix QR code expires (typically 15 minutes).

Response (200)

{
  "success": true,
  "data": {
    "transactionId": "tx_1719000000_xyz",
    "status": "PENDING_PAYMENT",
    "pixPayload": "00020101021226890014br.gov.bcb.pix...",
    "pixExpiry": "2026-07-01T18:15:00.000Z"
  }
}

Response (422 — wrong code)

{
  "success": false,
  "error": {
    "code": "MFA_INVALID_CODE",
    "message": "The TOTP code is invalid or has expired. Try again."
  }
}

After 5 consecutive failed TOTP attempts, the transaction is locked and the user must start a new one. Mippo files an alert internally.

Initiate a Pix to stablecoin transaction

Get status of a Pix to stablecoin transaction

Overview

KYC

Transactions

Partner

Confirm MFA for a pending transaction

Request

Response

​Request

​Response

Request

Response