NOMA / DEVELOPERSMerchant dashboard ↗

QR TERMINAL · TERMINAL

QR Terminal

In-store payments by QR. QR Terminal is a separate acceptance gateway: it works exactly like Acquiring, but has its own endpoints, fees and balance. Issue a payment QR in the merchant dashboard or by API.

01 · How it works

  1. Get the methods available to your store: GET /v1/terminal/payments/methods.
  2. Issue a payment: POST /v1/terminal/payments. Show qr_payload as a QR code at the till or send the customer to the checkout page.
  3. NOMA sends payment.paid to your webhook. You can also check GET /v1/terminal/payments/{id}.
  4. The amount minus the fee goes to your QR Terminal balance: terminal_rub, terminal_usdt. You withdraw it on request.

You can also issue a QR without code: dashboard → QR Terminal → Issue QR. Your storefront and the printed store QR code take payments through QR Terminal too.

Signing, idempotency and webhooks follow the common rules. QR Terminal must be enabled for your store separately from Acquiring.

02 · Methods

GET /v1/terminal/payments/methods

The response has the same format as GET /v1/payments/methods in Acquiring. The set of methods is configured for QR Terminal separately, and so are the requires_customer_phone and requires_customer_email flags.

03 · Issue a payment

POST /v1/terminal/payments
Idempotency-Key: 6f1c2b6e-terminal-1042

{
  "method": "sbp",
  "amount_minor": 150050,
  "merchant_order_id": "1042",
  "description": "Order #1042",
  "customer_phone": "+79001234567"
}

The body is the same as in Acquiring: method, amount_minor and the optional description, metadata, customer_email, customer_phone, merchant_order_id.

Buyer's phone and email. When the method has requires_customer_phone: true, send customer_phone in international format (+79001234567). When it has requires_customer_email: true, send customer_email. Without them the request fails with customer_phone_required or customer_email_required. Ask the buyer at the till before you issue the QR. See Buyer's phone and email. Since API 1.0.1.

04 · Payment object

The same object as in Acquiring, with "product": "terminal". Acquiring payments have "product": "acquiring".

{
  "id": "0b8f3c1e-…",
  "product": "terminal",
  "public_token": "…",
  "method": "sbp",
  "status": "pending",
  "currency": "RUB",
  "amount_minor": 150050,
  "qr_payload": "https://qr.nspk.ru/…",
  "payment_link": "…",
  "merchant_order_id": "1042",
  "expires_at": "2026-11-09T12:30:00+00:00"
}

05 · Confirm payment

GET /v1/terminal/payments/{id}

Statuses: pending, paid, paid_late, expired, cancelled. A QR Terminal payment is not available at /v1/payments/{id}, and the other way round.

06 · Webhooks

The same payment.* events as in Acquiring. Use the product field to tell QR Terminal payments apart.

07 · Balance and fees

GET /v1/balances

QR Terminal has its own balance accounts: terminal_rub and terminal_usdt. The fee is agreed for QR Terminal separately and fixed in the payment when it is created.

08 · Errors

HTTPCodeMeaning
403terminal_disabledQR Terminal is not enabled for your store
403kyb_requiredKYB is not approved yet
400customer_phone_required, customer_email_requiredSend the buyer's phone or email that the method requires
409idempotency_conflictThe key was used with a different body or in another product
503no_provider_availableNo method can take this amount right now

Other errors are the same as in Acquiring.