Scanpay · cards
Scanpay integration for Danish card payments
A Scanpay integration means your backend creates a payment in Scanpay and uses their payment window or API to capture cards, with ping and callback as the source of truth. Scanpay is a deliberately small product. That is a plus if you hate dashboards with 90 features. It is a minus if you think “payment integration” automatically includes MobilePay, Klarna and a subscription engine. Cards through Scanpay. MobilePay as its own product or through a gateway that has both. One checkout UI, two providers behind it, if that is what customers require. The transaction fee is Scanpay’s. Read the agreement.
7 min read · Updated 28 August 2026
A small gateway is often cheaper in development time. That is not the same as cheaper transactions, and it is not the same as a finished Danish checkout. Payments.
How to place a Scanpay integration correctly
Scanpay
- Cards, ping, callback
- Small product, short build time
- No assumption of MobilePay or Klarna
Beside it
- MobilePay as its own product
- Or a gateway that has both
- One checkout, two pipes — only if you need it
Is a small gateway cheaper?
Often yes in development time. The transaction fee is still theirs. A Ceptiv package from 18,000 DKK + 600 DKK/month covers the pipe. The fee per capture is in Scanpay’s agreement. Pricing.
Cards alone are rarely enough in Denmark
If your customers are Danish B2C, plan MobilePay as a second track — not as a feature you “just enable” in Scanpay. Write both pipes in the brief so the package holds the right number of integrations. Write to us.
FAQ: Scanpay integration
Is a small gateway the same as a cheaper integration?
Does Scanpay include MobilePay?
Ping or callback — which is the truth?
Can we add Klarna later?
Want us to build it for you?
You get a fixed-price proposal within 24 hours.
