SEB API Access — Sync Swedish Bank Data | open-banking.io
Pull live financial data from SEB (Skandinaviska Enskilda Banken) into your own product without wrestling with eIDAS certificates or bespoke bank onboarding. open-banking.io wraps SEB's PSD2 endpoints behind a single REST interface, so a Stockholm-based fintech and a cross-border SaaS tool call the exact same routes. Authenticate once, and SEB account data flows straight into your app.
How to connect SEB
- Create an open-banking.io account and generate your API key.
- Point a connection request at SEB using its BIC ESSESESS.
- Redirect the account holder to SEB's own login, where they approve access via strong customer authentication.
- Receive the consent token and start reading data immediately.
- Refresh the consent before it lapses to keep the link alive.
What data you can read
Once a customer has approved the connection, the API exposes:
- Accounts — IBANs, currency and metadata across business and personal profiles
- Balances — current and available figures, updated on request
- Transactions — dated, categorisable history for reconciliation, analytics or affordability checks
Consent and coverage
SEB grants a maximum consent window of 180 days, after which the customer re-authenticates to renew access. SEB is one of 2,600+ banks reachable through the same integration, so adding Nordea, Swedbank or any other European institution later means reusing code you already wrote — not building a new connector.
Privacy by design
The platform is zero-knowledge: credentials are entered only on SEB's own domain and are never visible to us or to you. There are no QWAC or QSEAL certificates to buy, host or rotate — that regulatory overhead sits with us, not your engineering team. You handle tokens; we handle compliance plumbing.
Pricing
Access starts at roughly EUR 3 per month, with SEB and every other supported bank included under the same flat subscription. No per-call surcharges and no separate SEB licence.
FAQ
Do I need an eIDAS certificate to reach SEB?
No. open-banking.io supplies the certified access layer, so you connect to SEB with a plain API key.
Which SEB customer types are supported?
Both business and personal accounts, using the same endpoints and the BIC ESSESESS.
How long does an SEB consent last?
Up to 180 days per approval; prompt the customer to re-authenticate to extend it.
Ready to integrate? Get started at open-banking.io.