QR Payment on Any Device: Pay from a Computer Screen or a Phone — It Just Works

A QR invoice does not care what screen it appears on. The same code that a customer sees on a desktop monitor at checkout works exactly as well on a phone in a Telegram chat. The payment details live inside the code, so the device only decides how the customer reaches their banking app — by tapping or by scanning. The transfer that follows is identical either way.

This matters because sellers rarely control where their invoice is opened. A link sent in a messenger might be read on a laptop at the office or on a phone on the bus. A code on a website is seen by desktop and mobile shoppers alike. With pmnt.app, a single generated invoice covers all of these cases without the seller producing anything different.

On a Phone: One Tap, No Second Device

When the customer is already on a phone — reading a chat, browsing a mobile site, looking at an emailed invoice — they do not need to scan anything. The QR invoice is also a payment link (a deeplink). Tapping it opens the banking app directly, with the transfer form already filled in: recipient IBAN, name, tax ID, amount, currency, and payment purpose.

If the phone has more than one banking app installed, the system asks which bank to pay from, then hands off to that app. From the customer's side the whole interaction is: tap → review → confirm. There is no camera, no aiming, no switching between two devices.

This is the most common path for invoices delivered through chat, social media, or email, where the recipient is holding the very device that can complete the payment.

On a Computer: Scan with the Phone in Your Pocket

When the customer sees the invoice on a computer — a checkout page on a laptop, an invoice open on a desktop monitor — the QR code is meant to be scanned. The customer opens any Ukrainian banking app on their phone, taps the QR scanner, and points the camera at the screen.

The phone recognizes the standard NBU QR format, opens the matching banking app, and pre-fills the same transfer form. The computer displays the request; the phone authorizes it. Money still moves directly between the two banks.

This split — show on the big screen, pay on the small one — is what lets an online store accept a bank transfer without ever asking the shopper to type an IBAN or leave the checkout to log into web banking.

Why the Same Code Works Everywhere

Device independence is not a feature pmnt.app bolts on — it falls out of the NBU standard the code follows.

  • One format, every compliant app. pmnt.app generates V003 QR codes to the National Bank of Ukraine specification. Every banking app in Ukraine that supports the standard reads the same fields the same way, so the customer's choice of bank does not change the outcome.
  • The code is structured data, not a picture. The IBAN, amount, and purpose are encoded inside the QR. The banking app decodes them locally on the payer's device, which is why the form arrives already filled whether it was tapped or scanned.
  • Link and code are two views of one invoice. The deeplink (for tapping) and the QR image (for scanning) carry the same payment request. The seller does not maintain two separate things — pmnt.app produces both from one invoice.

What the Seller Does Once

Because one invoice serves every device, the seller's job does not multiply with channels.

  1. Create the invoice once. Enter IBAN, name, tax ID, payment purpose, and (usually) an amount through the web interface, the Telegram bot, the API, or the MCP server for AI assistants.
  2. Get both an SVG code and a payment link. The QR renders as SVG for crisp display at any size — on a monitor, in a printout, or inside a web page.
  3. Deliver it wherever the deal happens. Show it on a screen, print it for a counter, paste it into a chat, embed it on a checkout page, or post it on social media. Whether the customer ends up on a phone or a computer, the same invoice does the job.

The Same Outcome on Either Path

Regardless of whether the customer tapped a link or scanned a code, the rest is the same:

  • Nothing is typed. All fields arrive pre-filled, so there is no mistyped IBAN and no wrong amount.
  • The customer verifies and confirms. They check recipient, amount, and purpose, choose the card or account to pay from, and authorize with PIN, fingerprint, or Face ID.
  • The transfer is direct. Money moves between the two banks with no intermediary holding it. Through SEP-4.1, instant transfers settle in roughly ten seconds, around the clock; amounts above 100,000 UAH route through standard channels and usually complete within an hour.
  • No merchant commission. A direct IBAN transfer carries no acquiring percentage, so the seller receives the full invoice amount on any device.

Practical Scenarios

  • Online store checkout. The shopper finishes an order on a laptop and sees the QR on the confirmation page. They scan it with their phone and confirm — no terminal, no card form, no leaving the page to open web banking.
  • Invoice in a chat. A freelancer sends a payment link in Telegram. The client, reading it on their phone, taps once and pays. The same link, opened on a desktop, shows a scannable code instead.
  • Printed at a counter. A market trader tapes a printed SVG QR to the stall. Every customer scans it from their own phone — the trader does not even need a device present.
  • Posted on social media. A creator publishes a QR for contributions. Followers on phones tap through; followers on computers scan. One post, both audiences.

What Still Requires a Phone and a Connection

Device independence has one fixed requirement: the actual payment is authorized on a smartphone with a banking app and an internet connection.

  • A computer can display the invoice, but it does not complete the payment — the confirmation happens in the banking app on the phone.
  • The payer needs to be online at the moment of payment; offline scanning is not supported.
  • The flow is built for hryvnia (UAH); foreign-currency settlement uses other methods.

Conclusion

The screen is just where the invoice is shown — it is not where the decision is made. On a phone, the customer taps the link and the banking app opens ready to confirm. On a computer, they scan the same code with their phone and pay from there. Either way the fields are pre-filled, the transfer goes straight to the seller's IBAN, and there is no merchant commission. For a seller using pmnt.app, that means creating one invoice and trusting it to work wherever the customer happens to open it — computer or phone, it all works.