Checkout and the ledger
The customer pays in MobilePay. The invoice is already in e-conomic or Dinero when you close the laptop.
Danish integrations
Payment, ledger, shipping, payroll, MitID, CRM, AI, SMS and Microsoft 365 — built into your own app. We reuse modules we have shipped before. You get a fixed price and a date.
The useful question is not “can you talk to e-conomic”. It is: who creates the invoice, when does MobilePay mark it paid, and who is allowed to see the CPR number. We write that mapping down before kickoff. That is how the price stays fixed.
International agencies treat e-conomic or MitID as “just another API”. They are not. Charts of accounts, Nemhandel, MobilePay agreements and MitID broker rules are local. We build the connection into your own Next.js app — not a WordPress plugin and not a redirect to someone else’s brand.
Small is 12 features and 1 integration. Medium is 24 and 2. Large is 36 and 3. Checkout plus the ledger is two integrations, even when it feels like one button. A first-time API we have not shipped before is heavier than a module we already have.
Deep guides
MitID and the ledger are the two decisions that change the rest of the build. The short pages below are the product. These two articles are the why.
MitID · signature
Login or a legally binding signature, inside your flow. Not an iframe with someone else’s brand.
Read the guidee-conomic · Dinero
Your app creates the invoice. The ledger is already waiting. One truth, not two windows.
Read the guideTypical combinations
A package includes 1, 2 or 3 integrations — Small, Medium, Large. Payment and bookkeeping are two, even when they feel like one checkout.
The customer pays in MobilePay. The invoice is already in e-conomic or Dinero when you close the laptop.
Receipt, parcel shop and tracking in the same mail. Shipmondo if you have more than one carrier. Direct PostNord or GLS if you only have one.
MitID inside the flow you already own — or Penneo / GetAccept if you already pay for a broker. The service page for MitID is under digital signature.
Name and address from cvr.dev while the customer types. The deal lives in HubSpot or Pipedrive. The invoice still belongs in the ledger.
Drafts, summaries and voice in your own product — not a chat tab beside it. Microsoft 365 if that is already where the files live.
56 platforms
One article per platform: the flow, the usual mistakes, and how it sits in a Ceptiv package. Not API docs.
Cards, MobilePay and pay-later. The customer pays in your flow — not in someone else’s shop. A gateway and MobilePay are often two products.
The invoice has to land in the system the accountant already opens. Do not switch ledger because a developer knows one API better.
Label, parcel shop and tracking in the same mail as the receipt. One carrier direct — or Shipmondo if you have several.
Payroll stays in DataLøn, Zenegy or Danløn. Your app sends hours or people. Salary on this site is Zenegy Salary.
A legally binding signature in the flow you already own. MitID white-label, or Penneo / GetAccept if you already have an agreement.
Leads, reviews and newsletters. HubSpot or Pipedrive as the truth — not a spreadsheet next to the app.
CVR lookup while the customer types. Name and address before you create the card.
Text, speech and images inside your own product. You own the flow, not the chat window.
Reminders, one-time codes and status texts. GatewayAPI is Danish. Twilio if you are already there.
Mail, files and Teams in Microsoft 365 — or Google, if that is the house. The system writes where you already work.
Short overviews
Shorter than the guides. Same systems, written for the search you already typed.