Vipps MobilePay QR safety
Vipps MobilePay provides payment links that merchants can share and can turn into QR images in the Business Portal. It also provides official QR flows for one-time payments, merchant redirects, merchant callbacks, and personal QR identification.
QR Code Crafter can make a supporting static QR that opens a provider-created payment-link URL through the phone camera or browser. It does not connect to Vipps MobilePay. It does not create an official Vipps or MobilePay in-app payment QR, call the QR API, create a payment session, receive callbacks, identify customers, process payments, or verify recipients.
For the most reliable branded payment experience, use the PNG or SVG generated by the Vipps MobilePay Portal, QR API, or your PSP. Do not copy or re-encode a provider-issued QR image or its qr.vipps.no destination.
Use this guide to distinguish shareable payment-link URLs from official payment QR flows and to test Danish MobilePay and Norwegian Vipps signs before publishing them.
Independent feature review
Reviewed on
Use QR codes safely with Vipps MobilePay payment links
Use a static browser-camera QR only for a provider-created payment-link URL. Official Vipps or MobilePay in-app payment QRs must come from the Portal, QR API, or PSP.
Key decisions
Provider-created payment links
Create the payment link in the Vipps MobilePay Portal. Use a separate static QR only when the provider documents that URL as shareable for the intended placement.
Official payment QR flows
Use the Portal, QR API, or your PSP for Vipps or MobilePay payment, merchant callback, merchant redirect, and personal QR flows.
Camera and browser scope
A static QR made here opens the payment-link URL through a phone camera or browser. Do not assume it behaves like an official QR scanned inside the Vipps or MobilePay app.
Short-lived payment sessions
One-time payment QRs expire in about 10 minutes. Generate them for the active checkout through the official provider flow and never print or reuse them.
Final payment preflight
Test the exact final artwork on real phones and verify the provider domain, recipient, amount, currency, description, expiry, and fallback before publishing.
Choose the right MobilePay or Vipps QR workflow
| Payment job | Best QR destination | Check before publishing |
|---|---|---|
| Provider payment-link URL | Provider-created Vipps MobilePay payment-link URL documented as shareable for the placement | Prefer the QR image generated in the Portal; otherwise test camera and browser opening before print |
| Danish or Norwegian payment sign | Official Portal QR or a supporting browser-camera QR for a documented shareable payment-link URL | Check local wording, provider domain, currency, recipient, and app/browser behavior with local users |
| One-time checkout payment | Official one-time QR or payment URL generated by Vipps MobilePay, your PSP, or the checkout platform | Do not reuse one-time or session-bound QR codes on posters, invoices, stickers, or counter signs |
| Invoice or donation page | Public page that leads to the provider payment step and is controlled for the full printed lifetime | Keep provider payment URLs unchanged and print fallback instructions near the code |
| Merchant callback or customer ID QR | Provider-generated QR flow from the Vipps MobilePay platform or QR API | Use the official flow when the merchant system must receive scan events or customer identifiers |
| Campaign measurement | UTM-tagged landing page before the payment step when the payment link should stay untouched | Do not add unsupported tracking parameters to wallet, checkout, or PSP payment URLs |
| Print production | SVG, PDF, or EPS for high-resolution invoices, receipts, posters, stickers, and counter cards | Scan the final proof from the real distance and verify recipient, amount, and description |
When to use QR Code Crafter for MobilePay and Vipps
Use a supporting static QR only for a public page or provider-created payment-link URL documented as shareable. Use Vipps MobilePay or the PSP for official payment and integration QR flows.
Supporting payment-link URL QR
Paste a provider-created payment-link URL only when its documentation allows sharing it for the intended placement. This creates a browser-camera QR, not an official in-app payment QR.
Provider-generated QR image
When the Portal, QR API, or PSP supplies a QR image, use that official PNG or SVG instead of copying its destination into another generator.
Official integration QR
Use the official provider flow when a scan must create a payment, expire with a session, send a callback, redirect through the provider, or identify a customer.
Supporting public pages
Use QR Code Crafter for a public product, invoice, donation, or instruction page you control before the provider payment step, then keep the payment URL and official QR untouched.
MobilePay and Vipps payment QR preflight
Payment QR codes need stricter QA than ordinary links because a wrong QR can send users to the wrong recipient or a dead payment session.
Recipient and market verification
Scan the QR code and confirm the displayed recipient, market, currency, product name, amount, VAT, and payment description before publishing.
App and browser fallback
Test the phone camera and browser path separately from scanning inside the MobilePay or Vipps app. A supporting static QR is not an official in-app QR.
Expiry and session rules
One-time payment QRs expire in about 10 minutes. Never print or reuse one-time, checkout-session, or short-lived payment URLs.
Artwork and scan distance
Use vector formats for print, protect the quiet zone, and scan the final sticker, invoice, table card, counter display, or receipt proof.
MobilePay and Vipps QR checklist
- Create the payment link in the Vipps MobilePay Portal and use its generated QR image where possible.
- Use a static URL QR only when the provider documents the payment-link URL as shareable for that placement.
- Do not copy or re-encode a provider-issued QR image or its qr.vipps.no destination.
- Do not use QR Code Crafter to create one-time payment QR codes, merchant callback QR codes, or customer identification QR flows.
- Scan the QR code on real phones and verify recipient, market, currency, amount, and description before printing.
- Use local Danish or Norwegian wording on customer-facing signs, including QR-kode, betalingslink, or betalingslenke where appropriate.
- Test the phone camera/browser path separately from the official in-app scan path.
- Avoid adding unsupported tracking parameters directly to payment links or PSP URLs.
- Use a UTM-tagged landing page before the payment step when campaign measurement is required.
Guides: print
Vipps MobilePay QR safety should be treated as a publishing workflow, not only a generated image. Confirm the destination, choose the export format, test the finished asset, and assign an owner before it appears in public material.
Before using Vipps MobilePay QR safety in print, packaging, signage, email, documents, apps, or automation, keep a release note with the encoded value, file name, export format, placement, owner, and test result. That record makes later corrections possible.
URL QR code: HTTPS
For Vipps MobilePay QR safety, verify that the encoded URL, contact detail, payment instruction, file, or app action is accurate, controlled by the right team, available on mobile, and appropriate for the people who may scan it.
Select format
Keep SVG, PDF, or EPS masters for print, packaging, signs, and design tools. Use PNG, JPG, WebP, or SVG for websites, email, documents, and digital placements, and avoid unexpected compression of the final code.
scan
Scan the browser preview, downloaded file, placed layout, exported PDF, CMS upload, email preview, and physical proof from realistic distances, angles, lighting, and devices before release.
Company
Record the QR owner, destination, source file, export format, placement, publish date, test devices, review date, and replacement trigger so long-lived static codes remain trustworthy.
QR code API
When many QR files are needed, use consistent names, manifest checks, OpenAPI or WebMCP parameters, and output-format validation before handing assets to design, print, or content teams.
static vs dynamic QR codes
Review Vipps MobilePay QR safety after campaign changes, rebrands, domain moves, payment-detail updates, app-store changes, document migrations, or analytics changes so public QR codes do not point to stale or unsafe destinations.
Feedback
Add readable destination text, a short URL, support contact, or printed instruction where scanning is business-critical, accessibility-sensitive, or likely to happen with poor connectivity.
Accessibility
Place nearby text that explains the scan action, keep contrast high, avoid tiny placements, and ensure the destination works with mobile browsers, screen readers, reduced-motion settings, and keyboard navigation.
How to publish a Vipps MobilePay QR safely
- 1
Create the payment link with the provider
Create the payment link in the Vipps MobilePay Portal or your PSP and confirm its recipient, amount, currency, description, validity, and sharing rules.
- 2
Choose the official or supporting QR
Use the provider-generated PNG or SVG for an official payment QR. Use QR Code Crafter only for a documented shareable URL that should open through the phone camera or browser.
- 3
Test the exact final placement
Test the final artwork on real phones, confirm the expected camera, browser, and app behavior, and verify recipient, amount, currency, expiry, and fallback.
Frequently asked questions
Can QR Code Crafter create an official MobilePay or Vipps QR code?
No. QR Code Crafter does not connect to Vipps MobilePay, call the QR API, create payment sessions, receive callbacks, identify customers, or process payments. Use the Portal, QR API, or your PSP for official QR flows.
Can I make a QR code for a MobilePay or Vipps payment link?
Yes, when the provider created the payment link and documents its URL as shareable for that placement. Prefer the QR image generated in the Portal. A QR made here opens the URL through the phone camera or browser and is not an official in-app payment QR.
What should Danish and Norwegian payment signs say?
Use clear local wording around the QR code, such as MobilePay QR-kode or MobilePay betalingslink in Denmark and Vipps QR-kode or Vipps betalingslenke in Norway. Keep the recipient name, currency, amount rules, and fallback instructions visible near the code.
Should I print a one-time payment QR code?
No. Vipps MobilePay documents that one-time payment QRs expire in about 10 minutes. Generate them for the active checkout through the official provider flow and never print or reuse them.
Can I add tracking to a MobilePay or Vipps QR code?
Use a UTM-tagged landing page before the payment step when measurement is required. Do not modify wallet, checkout, PSP, or payment-link parameters unless the provider documents that they are supported.
Which file format should I download?
Use SVG, PDF, or EPS for printed payment signs, table cards, stickers, invoices, and receipts. Use PNG, JPG, or WebP for digital payment instructions.