Paylike · cards
Paylike integration: card payments in your system
A Paylike integration means your frontend tokenises the card through Paylike, and your backend captures, refunds and listens for transaction status. Teams pick Paylike when they want a simple card API rather than a full merchant universe. That is a strength if checkout is simple. It is a weakness if in six months you need MobilePay, marketplace split payments and Danish acquirer support in the same pipe. We put the public key in the frontend, the secret on the server, lock the amount in the backend and confirm capture before you mark the order paid. The transaction fee is Paylike’s. The build is the flow in your system.
Paylike is a card layer. It is rarely the whole Danish checkout. If 70 percent of your customers ask for MobilePay, start with QuickPay integration or PensoPay. Payments and gateways.
Build a Paylike integration like this
- Public key in the frontend, secret on the server. Never the other way around.
- Amount and currency are locked in the backend, not in the browser.
- A webhook or pull confirms capture before you mark the order paid.
- Refund is a first-class action in admin — not a script only you know.
Paylike fits
- One currency, one card flow, few methods
- You do not want a large merchant dashboard
- PCI via their fields, not your own inputs
Choose a Danish gateway
- Customers ask for MobilePay
- You need split payments or a marketplace
- You want to call Danish support about settlement
PCI without homemade card fields
If you use Paylike’s fields and tokenisation correctly, you never touch PAN. That is the point. Do not build your own card fields “for the design”. That moves PCI responsibility back to you. MobilePay integration covers the Danish button Paylike typically does not have.
The transaction fee is in Paylike’s agreement. A Ceptiv package from 18,000 DKK + 600 DKK/month builds the pipe, not the fee per capture.
When checkout has to grow in six months
Write down the methods you know are coming: MobilePay, Apple Pay, subscriptions, partial capture. If the list is longer than “cards now”, pick the gateway first. Tell us in contact so you do not pay for a card layer you rip out later. See packages.
FAQ: Paylike integration
Are we PCI compliant with Paylike?
If you use their fields and tokenisation correctly, you never touch PAN. Do not build your own card fields for the design.
Can Paylike replace MobilePay?
No. Paylike is a card layer. Danish customers often expect MobilePay next to it.
Where should the amount be locked?
In the backend. An amount the browser can change is not a payment. It is a hole.
Can refunds only happen in Paylike’s dashboard?
Technically yes if you do not build it. Commercially no. Refund should be a button in your admin.