Danish integrations

40+ integrations already built — so you pay for the product, not the plumbing

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.

An integration is a flow, not a logo on the website

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.

Why Danish APIs are a separate skill

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.

How many integrations a package actually holds

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.

Typical combinations

Most projects are two or three systems talking

A package includes 1, 2 or 3 integrations — Small, Medium, Large. Payment and bookkeeping are two, even when they feel like one checkout.

Shop with labels

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.

A signature in your own brand

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.

Sales that does not type CVR twice

Name and address from cvr.dev while the customer types. The deal lives in HubSpot or Pipedrive. The invoice still belongs in the ledger.

AI in the daily work

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

What we actually connect

One article per platform: the flow, the usual mistakes, and how it sits in a Ceptiv package. Not API docs.

All 56 integration guides

Payments

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.

Accounting

The invoice has to land in the system the accountant already opens. Do not switch ledger because a developer knows one API better.

Shipping

Label, parcel shop and tracking in the same mail as the receipt. One carrier direct — or Shipmondo if you have several.

Payroll

Payroll stays in DataLøn, Zenegy or Danløn. Your app sends hours or people. Salary on this site is Zenegy Salary.

Signature

A legally binding signature in the flow you already own. MitID white-label, or Penneo / GetAccept if you already have an agreement.

CRM and marketing

Leads, reviews and newsletters. HubSpot or Pipedrive as the truth — not a spreadsheet next to the app.

CVR and data

CVR lookup while the customer types. Name and address before you create the card.

AI

Text, speech and images inside your own product. You own the flow, not the chat window.

SMS and voice

Reminders, one-time codes and status texts. GatewayAPI is Danish. Twilio if you are already there.

Workspace

Mail, files and Teams in Microsoft 365 — or Google, if that is the house. The system writes where you already work.

Short overviews

Five integrations as their own service page

Shorter than the guides. Same systems, written for the search you already typed.