SEB - Företag API Integration & Open Banking

ERP and automated bookkeeping

Companies using Enkelbok or other accounting software need to sync SEB Corporate transactions into their books. Open Payments and SEB offer direct ISO 20022 integration for automated bookkeeping; connection is typically ready within three business days. Our API can expose transaction export (date range, account, type) with fields suitable for Excel/CSV or JSON import. Flow: SEB Företag / Business Arena → auth (BankID/session) → our API or file integration → ERP. This maps to Open Banking: structured account and transaction data with consent.

Liquidity and treasury dashboard

Finance teams want a single view of balances and liquidity development across multiple companies (Enkla firman, limited companies). We deliver endpoints that return balance per account and liquidity chart data (development over time). Data maps to Open Data: aggregated balances and time-series liquidity; typical fields include company_id, account_id, balance, liquidity_snapshot[]. Use: cash forecasting, internal reporting, and consolidation.

Payment authorization and approval workflow

Businesses need to integrate “authorise filed payments and orders registered by other users” into approval workflows or audit logs. Our implementation can expose payment orders pending approval (with consent and appropriate roles). This fits PSD2 payment initiation and account information: who authorised what and when. Fields: order_id, amount, recipient, status, authorised_by, timestamp.

Invoice and Bankgiro reconciliation

Accounts payable or accounting teams need to match OCR-paid invoices and same-day Bankgiro payments with internal records. We deliver endpoints that return payment metadata (OCR number, amount, recipient, date) and incoming Bankgiro items. Data flow: app → BankID/session → API → your reconciliation engine. Aligns with Swedish payment infrastructure (Bankgirot) and PSD2 account access.

Multi-bank and TPP aggregation

Third-party providers (TPPs) with AISP/PISP licences need to aggregate SEB Corporate data alongside other Swedish banks (e.g. Swedbank, Nordea, Handelsbanken). SEB’s Developer Portal provides PSD2 Account Information and Payment Initiation APIs; we can complement with protocol analysis for app-specific flows (e.g. multi-company switch, liquidity chart) and deliver a unified API layer. Consent and SCA (BankID) are central; we document auth flows and error handling for production.

Deliverables

• API specification (OpenAPI / Swagger)
• Protocol and auth flow analysis (BankID, session, token)
• Runnable API source code (Python / Node.js) for statements, balances, liquidity, payments
• Test scripts and interface documentation
• Compliance notes (PSD2, GDPR, consent, retention)

Example: transaction statement (pseudo)

GET /api/v1/seb-foretag/statement
Authorization: Bearer <ACCESS_TOKEN>

Query: company_id, account_id, from_date, to_date (e.g. 25 months back)

Response: {
  "account_id": "...",
  "transactions": [
    { "date": "2025-02-10", "amount": -1200.50, "counterparty": "...", "reference": "OCR ..." }
  ],
  "balance_after": 45000.00
}

Example: balance and liquidity (pseudo)

GET /api/v1/seb-foretag/balances
Authorization: Bearer <ACCESS_TOKEN>

Response: {
  "companies": [
    { "company_id": "...", "accounts": [ { "account_id": "...", "balance": 125000.00 } ] }
  ]
}

GET /api/v1/seb-foretag/liquidity?company_id=...&from=...&to=...
→ liquidity_snapshots[] (date, value) for chart

Example: auth and errors (pseudo)

// BankID / session-based auth (pseudo); PSD2 TPP uses OAuth2 + SCA
POST /api/v1/auth/consent  → redirect to BankID / SEB consent
Callback: access_token, refresh_token, expires_in

Response 401: { "error": "consent_expired", "message": "Re-authenticate with BankID" }
Response 403: { "error": "scope_insufficient", "message": "Requested scope not granted" }

Compliance & privacy

We work from client authorization or public/authorized APIs and follow privacy and local regulations. For SEB - Företag and Swedish corporate banking, we align with PSD2 (Payment Services Directive 2): third-party access to account information and payment initiation requires appropriate AISP/PISP licensing and customer consent. GDPR applies to personal data processed in the EU/EEA; we recommend consent records, purpose limitation, data minimization, and secure transmission. SEB’s Developer Portal and open-source openbanking documentation support compliant integration; our deliverables include guidance on consent and retention.

Data flow / architecture

A typical pipeline we design: (1) Client app (SEB Företag or your front-end) — user consents (e.g. BankID) and triggers requests. (2) Ingestion / API layer — our delivered service authenticates (BankID/session or PSD2 OAuth2), validates scope, and queries SEB’s APIs or app-derived data. (3) Storage or cache (optional) — for aggregation, reporting, or ISO 20022 file generation. (4) Output — JSON/API or file export to your ERP, dashboard, or TPP. Logs and consent are retained for audit and regulatory compliance.

Market positioning & user profile

SEB - Företag targets B2B users in Sweden: owners of limited companies (aktiebolag), sole traders (enskild firma), and other company forms using SEB’s Enkla firman (internet office for companies). The app is available in English and Swedish on Android and iOS (package se.seb.enklafirman). As of 2025 it had over 100,000 downloads with a 5.0-star rating. In the same ecosystem, Nordea Business SE, Swedbank’s app for företag, and Handelsbanken corporate mobile services serve similar segments; SEB’s Developer Portal integrates with aggregators such as Plaid, enable:Banking, and TrueLayer for open banking use cases.

About us

We are a technical studio focused on app interface and authorized API integration. We deliver protocol analysis, Open Data integration, third-party integration, and automated scripting plus API documentation. Services start at $300; we can deliver first and you pay when satisfied.

• Experience in fintech and mobile apps (Sweden and overseas)
• Android and iOS; ready-to-use API source and docs
• Transparent pricing; result-first option

Contact

For inquiries, quotes, or to send your target app and requirements:

Contact us

Process

1. Confirm needs: app name (SEB - Företag) and integration scope (transactions, liquidity, invoices, multi-company).
2. Protocol analysis and API design (2–5 days, depending on scope).
3. Development and validation (3–8 days).
4. Delivery of docs, samples, and tests (1–2 days).
5. Typical first delivery: 5–15 business days.

FAQ

What do I need to provide?

How long until delivery?

Compliance and privacy?