Nordic integrations,
built for smaller companies.
Payments, national eID, accounting, e-invoicing and shipping — the services your customers already expect you to support. We connect them at a scale a twelve-person company can actually pay for: a lean build, then a small monthly fee to keep it working.
- Markets
- NO · SE · DK · FI
- Pricing
- Build, then monthly
What we connect.
Six areas, and in most projects you need two or three of them — not the whole list.
-
Payments and checkout
Customers pay the way they already pay.
Vipps MobilePay
Stripe
Klarna
Apple Pay and Google Pay are not separate projects — they arrive as wallets inside Stripe or Vipps once that is in place. Worth knowing before anyone quotes you for them.
Wallets come included
-
National eID and signing
People sign in and sign documents with the ID they already carry.
BankID (NO, SE)
MitID (DK)- FTN (FI)
Signicat
None of these are self-serve. For a smaller company the practical route is a broker rather than four separate contracts — we build against the broker and keep the option to go direct later.
Agreement required
-
Accounting
Invoices raised, payments reconciled, nothing re-typed.
Fiken
Tripletex
PowerOffice Go
Conta
Visma eAccounting
24SevenOffice
Unimicro
What Nordic small companies actually run on — and the part of this page with the least standing in the way.
Documented, open APIs
-
E-invoicing
Sell to the public sector without being turned away on format.
PEPPOL- EHF (NO)
You do not integrate PEPPOL directly — you join through an access point, and the format work sits behind that. If you sell public this stops being optional, so we usually do it first rather than last.
Via an access point
-
Shipping
Labels, tracking and delivery notices without opening a courier portal.
Bring
PostNord
DHL
Printed and sent from inside your own system, so nobody re-types an address that you already hold.
Runs in your own system
-
The systems your team already has open
The notification lands where people already are.
Microsoft 365
Teams
Slack
HubSpot
monday.com
Instead of in a system they open twice a week. Usually the most visible change on this page for the least work.
Cheapest work here
We did this to ourselves first.
Every integration on this list is one we have either shipped in our own product or run in production for a client. That product is Pactly: live in Norway, Sweden, Denmark, Finland and the EU, signing with each country’s national eID, payments switched on. It is also why we can tell you up front which connections are quick and which ones mean a month of waiting on someone else’s approval.
How it runs.
-
01
Discovery
We map the process end to end and find which systems actually have to talk. Often fewer than the brief assumed.
-
02
Design
What happens when the other side is down, returns a duplicate, or changes its API without telling you. Integrations fail at the edges, so that is where the design effort goes.
-
03
Build and go live
Built, tested against the real service rather than a mock, deployed with monitoring and documentation your own developer can pick up.
-
04
Keep it working
APIs move. A small monthly fee covers monitoring, version updates and the fixes that follow — instead of an annual contract sized for a company ten times larger.
Becoming an official integration partner.
If you are building a Nordic SaaS product, listing in a platform’s partner programme changes how buyers see you. The work is mostly unglamorous: meeting the technical requirements, writing the documentation they ask for, tightening authentication, and answering review questions until it passes.
We have been through this for our own product rather than only for clients, which is the part worth hiring. What we will not do is promise an outcome that the platform decides — approval is theirs, not ours.