// FAQ

Frequently Asked Questions

A QR code can provide convenient access to a financial portal, but it does not make the destination safe. Use an authenticated first-party domain, protect sensitive documents behind access controls, monitor for tampering, and give customers a separate way to verify the institution before entering credentials or payment details.

Client-side generation can reduce exposure of the encoded URL, but the site must be checked for analytics, logging, third-party scripts, and other network requests before making that promise. Never place secrets or reusable access tokens in a visible symbol; use an authenticated portal and documented privacy controls.

Yes. The Bitcoin type builds payment links for a receiving address, with an optional amount, for the coins listed in the generator. The generator cannot verify the address, so check it in your wallet before printing, and remember that crypto payments cannot be recalled.

Show the institution name and expected first-party domain beside the symbol, and repeat them on the landing page before requesting information. Customers should preview unfamiliar destinations and stop after unexpected redirects. Payment or identity flows should use authenticated systems, monitoring, and established fraud-response channels.

Account numbers, balances, statements, client identifiers, document links and session tokens. Anyone who photographs a mailer can decode the symbol, so the code should hold only a front-door address, with identity and access controls applied by the portal after the scan.

It depends on the firm, country and activity. Examples to ask compliance about include FINRA Rule 2210 and recordkeeping rules, UK FCA rules, the GLBA Safeguards Rule, GDPR and PCI DSS. A QR code does not satisfy any of them by itself.

Link to a hosted checkout from a PCI DSS compliant provider so your firm does not handle card data, and print the provider domain or your own beside the code. Keep payment links separate from login links, and see the guide on accepting QR code payments.

Common patterns include fake stickers over legitimate codes, look-alike domains and spoofed login pages. UK Action Fraud logged 784 QR phishing reports from April 2024 to April 2025, per press coverage. Print your domain, add a never-ask warning and inspect public signs.