QuickPay · gateway

QuickPay integration: a Danish payment gateway in a custom app

A QuickPay integration means your custom system takes cards — and usually MobilePay — through a Danish acquirer gateway that Danish shops already know. QuickPay is the pick when you want one settlement, Danish support and an API that was not designed for Silicon Valley subscriptions first. You can host the payment page in your own look or use QuickPay’s window. 3-D Secure sits with the gateway. Webhooks tell you when an amount is captured, refunded or charged back. Ceptiv builds the gateway into your system at a fixed price — you do not have to move onto WooCommerce to make it work.

If you already have a QuickPay agreement from an old shop, it is often cheaper to keep it than to switch to Stripe in the middle of a system project. Payments at Ceptiv.

Jeres checkout
MobilePay
Kort
Hosted QuickPay window or your own look — same order id, same webhook back.

What you gain by building QuickPay in

  • A payment page in your own look — or QuickPay’s hosted window
  • Cards, MobilePay and often Apple Pay/Google Pay on the same agreement
  • 3-D Secure handled by the gateway
  • Webhooks on capture, refund and chargeback
  • The option to authorise now and capture later

When QuickPay beats Stripe

QuickPay wins when

  • You settle in DKK to a Danish bank and want Danish support
  • You already have a QuickPay agreement from an old shop
  • You need MobilePay without adding a second product
  • The accountant wants a Danish statement

Stripe wins when

  • You sell subscriptions across countries
  • You want Billing, Tax or Connect in the ecosystem
  • You can live with English onboarding
  • Complex seats and trials are the core
Either can be right. Choose by the till, not by Hacker News.

What to lock before kickoff

  1. You have a QuickPay agreement and API key — or you create them in week 1
  2. You know whether you capture immediately or only reserve
  3. You know who is allowed to refund in admin
  4. VAT and currency match on the order and in the gateway
Events
payment.capturedok
invoice.bookedok
click.paidignore
Capture, refund and chargeback land as events. Your database owns “paid”.

QuickPay counts as one integration in a Ceptiv package. Small is DKK 18,000 plus DKK 600/month. If you also want MobilePay as a separate product, that is two. See pricing.

If you already have a QuickPay agreement, put the merchant id in the brief. Then we do not guess at acquirer and MobilePay add-ons. Quote within 24 hours.

FAQ: QuickPay integration

Can QuickPay be used without WooCommerce?

Yes. The API exists for exactly that.

What about subscriptions?

Possible, but Stripe Billing is often more mature for complex seats and trials. Say so in the brief.

Can we capture later than the reservation?

Yes. Authorise-then-capture is one reason to pick a gateway over a plain payment link.

Who owns PCI?

A hosted window keeps PCI with QuickPay. A custom look needs a clear scope. We recommend hosted unless checkout is the product.