Stripe · cards and billing
Stripe integration in a Danish web app: cards, billing, webhooks
A Stripe integration means your system takes cards — and usually subscriptions — through Stripe Checkout or Stripe Elements, with webhooks as the truth about what was actually charged. Stripe is strongest when you have trials, seats and upgrades, or when you sell in several currencies. In Denmark it is weaker if the customer expects MobilePay as the first button, and if you “just want a Danish invoice in e-conomic when someone pays”. That last part you have to build. The architecture that does not fall over: your database owns the customer, Stripe owns the payment method, the webhook is the only source of “paid”.
If you write “paid” on click, you get support days and crooked numbers. That is the most expensive line in a Stripe project — and the easiest to avoid. Package pricing.
Where Stripe earns its keep
- Subscriptions with trial, seats, upgrades and downgrades
- Multiple currencies
- A large plugin ecosystem if you later need Identity, Tax or Connect
- A fast go-live if you can accept Stripe’s onboarding
Where Stripe is weaker in Denmark
- MobilePay as a first-time-customer expectation — more often solved with QuickPay or a separate MobilePay product
- “We just want a Danish invoice in e-conomic when someone pays” — you build that yourself
- Support in Danish
An architecture that does not tip over
- Your database owns the customer and the plan
- Stripe owns the payment method and the invoice object
- The webhook is the only source of “paid”
- e-conomic/Dinero update after the webhook, not after the button click
Stripe Checkout
- Hosted page, fast go-live
- PCI stays with Stripe
- Less control over the UI
Stripe Elements
- Fields in your own look
- More work, more scope
- Choose it when checkout is your product
1
source of truth for “paid” — the webhook
2
integrations if you also want MobilePay
24t
quote from Ceptiv
Stripe is one integration in the package. Small: DKK 18,000 + DKK 600/month. If you want both Stripe and MobilePay in the same checkout, that is two — the Medium package at 36,000 + 900. What custom software costs.
Send the plan: Checkout or Elements, and whether MobilePay should sit beside it. Then we price one checkout flow, not two loose plugs.
FAQ: Stripe integration
Should we use Stripe Checkout or Elements?
Checkout is fastest and easiest on PCI. Elements is for when checkout is the product.
Can we mix Stripe and MobilePay?
Yes, but that is two integrations. Plan it as one checkout flow.
When may e-conomic be updated?
After a verified webhook. Never after the click. Otherwise you invoice payments that never landed.
Does Stripe handle Danish VAT for us?
Stripe Tax can help, but your e-conomic invoice is still your job. Build the mapping, or keep VAT out of Stripe and inside the accounting system.
What about chargebacks?
The webhook must be able to set the order to “dispute” so you do not ship again. That is business logic, not a Stripe dashboard.