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
Built this way
Pactly
After go-live
Monthly, not annual

We did this to ourselves first.

Pactly is our own product: live across five markets, signing with each country’s national eID, payments switched on. Every integration below is one we have either shipped in it or run in production for a client — which is also why we can tell you which ones are quick and which ones will take a month of waiting on someone else’s approval.

See Pactly

What we connect.

Six areas, and in most projects you need two or three of them — not the whole list.

  1. 01

    Payments and checkout

    Vipps MobilePay, Stripe, Klarna. Between them they cover how Nordic customers actually pay. Apple Pay and Google Pay are not separate projects — they arrive as wallets inside Stripe or Vipps once that is in place, which is worth knowing before anyone quotes you for them.

  2. 02

    National eID and signing

    BankID in Norway and Sweden, MitID in Denmark, FTN in Finland, and document signing on top. None of these are self-serve: you need an agreement, and for a smaller company the practical route is a broker such as Signicat rather than four separate contracts. We build against the broker and keep the option to go direct later.

  3. 03

    Accounting

    Fiken, Tripletex, PowerOffice Go, Conta, Visma eAccounting, 24SevenOffice, Unimicro. These are what Nordic small companies actually run on, and their APIs are documented and open. Invoices raised automatically, payments reconciled, no re-typing.

  4. 04

    E-invoicing

    PEPPOL and the Norwegian EHF profile. You do not integrate PEPPOL directly — you join through an access point, and the format work sits behind that. If you sell to the public sector this stops being optional, so it is usually the first thing we do rather than the last.

  5. 05

    Shipping

    Bring, PostNord, DHL. Labels, tracking and delivery notifications printed and sent from inside your own system, so nobody re-types an address into a courier portal.

  6. 06

    The systems your team already has open

    Microsoft 365 and Teams, Slack, HubSpot, monday.com. Usually the cheapest work on this page and the most visible: the notification that lands where people already are, instead of in a system they open twice a week.

How it runs.

  1. 01

    Discovery

    We map the process end to end and find which systems actually have to talk. Often fewer than the brief assumed.

  2. 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.

  3. 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.

  4. 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.