Make a payment

Make a payment

Confirm payment using the lock returned in preview.

This operation is asynchronous. Do not assume a final business result from the creation response alone.

Use POST /crypto/v2/synthetics/qr-payment to execute settlement.


Example request

curl -X POST https://sandbox.manteca.dev/crypto/v2/synthetics/qr-payment \
  -H "md-api-key: $MD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
      "qrCode": "fa44218d-7b3c-4a1e-bc9f-2d5e8f01c3a7",
      "externalId": "my-external-ref-001"
  }'

Response

{
      "id": "65b2c3d4e5f6a7b8c9d0e1f2",
      "numberId": "98765",
      "externalId": "my-external-ref-001",
      "companyId": "64a1b2c3d4e5f6a7b8c9d0e1",
      "userId": "64a1b2c3d4e5f6a7b8c9d0e2",
      "userNumberId": "12345",
      "status": "STARTING",
      "type": "QR3_PAYMENT",
      "details": {
          "depositAddress": "0x1a2b3c4d5e6f...",
          "paymentAssetAmount": "15000.00",
          "paymentAsset": "ARS",
          "paymentAgainstAmount": "12.00",
          "paymentAgainst": "USDT",
          "paymentPrice": "1250.50",
          "price": "1250.50",
          "priceExpireAt": "2026-02-21T15:30:00.000Z",
          "qrType": "QR3"
      },
      "currentStage": 0,
      "stages": {
          "0": {
              "stageType": "ORDER",
              "asset": "USDT_ARS",
              "operation": "SELL",
              "amount": "12.00"
          },
          "1": {
              "stageType": "WITHDRAW",
              "address": "...",
              "network": "QR3"
          }
      },
      "creationTime": "2026-02-21T15:25:30.000Z",
      "updatedAt": "2026-02-21T15:25:30.000Z"
  }

Request fields

FieldRequiredDescription
qrCodeYesLock code returned by POST /crypto/v2/payment-locks. It expires, so execute promptly after the preview. paymentCode is accepted as an alias.
externalIdNoYour unique identifier for this payment. Recommended: a value already used returns 409 SYNTHETIC_EXISTS and creates nothing.

The payer comes from the lock: the user in userAnyId, or the sender you declared there under the Principal Accounts model. This endpoint does not take userAnyId.


Execution behavior

Execution debits the balance defined by against in the preview lock and applies conversion when needed.

The internal deposit step in the synthetic can be optional depending on your company configuration. Consult your integration manager for details.

Typical synthetic lifecycle:

  • starts in STARTING → ACTIVE,
  • usually reaches COMPLETED or CANCELLED after execution.

If execution fails at the payment provider, the synthetic moves to CANCELLED and funds are reverted. The failure code is recorded on the failing WITHDRAW stage's errors array of the synthetic — in the same place both in GET /v2/synthetics/{syntheticAnyId} and in the SYNTHETIC_STATUS_UPDATE webhook payload:

"stages": {
    "2": {
        "stageType": "WITHDRAW",
        "errors": ["P4: Payment blocked by receiver"]
    }
}

Each entry is formatted as <code>: <description>. See Payment failure codes for the full list (P1 to P8) and how to react to each one.



Track status

MethodEndpoint
PollGET /v2/synthetics/{syntheticAnyId}
ListGET /v2/synthetics
WebhookSYNTHETIC_STATUS_UPDATE, PAYMENT_REFUND

After successful execution, later refunds are still possible. Partial refunds keep the synthetic COMPLETED; only a fully refunded outcome moves it to CANCELLED. See After the payment for webhook payloads and refund handling.


For fiat payout destination requirements by country (bank codes, account formats, etc.), see Third-party Transfers.


Did this page help you?