MobilePay · payments
MobilePay integration in your own system
A MobilePay integration lets the customer pay from inside your order, invoice or checkout flow using the app already on their phone. In Denmark that is often the method that cuts the most abandoned carts, because nobody has to type a card number. There is no single MobilePay button. You buy a product from Vipps MobilePay and you build the flow in your own system: Checkout for a shop, Invoice for a payment link, or Subscriptions for recurring charges. If the webhook never writes status back into your database, you only have a link — and you will chase people who already paid. Ceptiv wires the product into your custom system at a fixed price.
That is the sentence most Danish SMEs are searching for. The rest of this page is the product choice, the mistakes that create support tickets, and how MobilePay talks to e-conomic or Dinero afterwards. See payment modules.
Which MobilePay product you actually need
Pick the product by when money should leave the account — not by what a developer has used before.
| Product | Used for | Typical SME case |
|---|---|---|
| MobilePay Checkout | Cards + MobilePay in a shop | Webshop, booking, tickets |
| MobilePay Invoice | Payment link on an invoice | Trades, B2B, service firms |
| MobilePay Subscriptions | Recurring charge | Membership, retainers, subscriptions |
What the integration actually does
Order locks
Amount, currency and reference are written before the customer sees MobilePay.
App or QR
The customer opens the MobilePay app or scans a QR on desktop.
Webhook
Vipps sends captured, rejected or expired. You verify the signature.
Status written back
Your system shows paid and can trigger posting in e-conomic or Dinero.
- Creates a payment once the order is locked
- Sends the customer into the MobilePay app or shows a QR
- Receives a webhook when the amount is captured, rejected or expired
- Writes status back into your system
- Can trigger posting in e-conomic or Dinero afterwards
Mistakes that create tickets
- The brief mixes Invoice and Checkout as if they were one product
- Amount caps and DKK-only rules on some products get ignored
- You test 200 times with a private MobilePay and no sandbox
- The UI shows “paid” before the webhook is verified
What it costs
Vipps MobilePay charges its own transaction fees (a percentage plus often a krone — check current terms). That is not the studio’s markup. The build is getting the flow into your system. At Ceptiv, MobilePay is a finished module and can sit as the single integration in the Small package: DKK 18,000 plus DKK 600/month. Medium is 36,000 plus 900 and two integrations. Large is 54,000 plus 1,200 and three. See pricing.
Tell us whether you need checkout, an invoice link or a subscription. You get a fixed quote within 24 hours. MobilePay as a service.
FAQ: MobilePay integration
Can we use MobilePay without a webshop?
Yes. The Invoice flow is built for invoices and jobs — not only baskets.
Does it work with e-conomic?
Yes, if you also integrate the accounting system. Payment and posting are two integrations that should be scoped as one flow.
Is Apple Pay the same thing?
No. Apple Pay and Google Pay usually ride a gateway (QuickPay, Stripe). MobilePay is its own product.
Do we have to verify the webhook?
Yes. Never show “paid” from a redirect alone. Redirects can be spoofed. The signed webhook is the source of truth.