Embedded Finance Build Day — Stockholm — 25 Aug 2026 ↗

Build with
Open Payments

Access banking data and payment infrastructure through one unified API — and turn your idea into a working prototype during Build Day.

Create Sandbox accountExplore documentation
01
Account information
Accounts, balances, transactions Or why not verify account owners or verify ledgers?
02
Payment initiation
Domestic, SEPA, cross-border, Single or Batch. Simply all kinds of payments.
03
ISO & banking infrastructure
Open Payments is fully integrated with banks ISO products. Feel free to build automation or enjoy enriched data-points.

Get your access token

Zero to first API call in 5 min →
sandbox auth
curl -X POST "https://auth.sandbox.openbankingplatform.com/connect/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "grant_type=client_credentials" \
  -d "scope=accountinformation corporate"

01 What can I build?

Building blocks for financial applications

Open Payments integrates with the banks' APIs and presents one harmonised REST API. Here is what is available to your team on Build Day.

  1. 01

    Account Information

    List accounts for a private PSU or a corporation, then pull account details, balances and transactions through an active consent.

    [ Accounts ][ Balances ][ Transactions ][ private / corporate ]

    Good for dashboards, cash-flow tools, reconciliation, lending context and financial decision support.

    Consent & Account Information
  2. 02

    Payment Initiation

    Initiate payments from bank accounts. The platform handles the bank integration layer so your team can focus on the product experience.

    [ Domestic ][ Swedish giro ][ SEPA ][ Cross-border ][ Future payments ]

    For most banks, both single payments and Signing Baskets for signing several payments in one go.

    Payments quick start
  3. 03

    ISO Payments

    Send structured payment instructions to the API and let Open Payments generate the underlying ISO 20022 pain.001 payment file.

    [ pain.001 ][ ISO 20022 ]

    Interesting for ERP, finance and payment automation, treasury, accounts payable and embedded finance.

    ISO Payments
  4. 04

    FX & Cross-border

    Create FX quotes for cross-border payments, with spot and forward rates available through FX Connect.

    [ FX quote ][ Spot ][ Forward ][ Cross-border ]

    Check the FX Connect docs for the currencies, rate types and flows currently supported.

    FX Connect
  5. 05

    Bankgiro enrichment

    Enrich account information with Swedish Bankgiro data using the bankgiroinformation scope alongside accountinformation.

    [ bankgiroinformation ][ Bankgiro Lookup ]

    Useful for reconciliation, supplier and customer identification, cash management and payment intelligence.

    Bankgiro Lookup
  6. 06

    Bank discovery

    Use the ASPSP Information Service to discover which banks are available for a country and what capabilities they expose in the Open Payments ecosystem.

    [ aspspinformation ][ Capabilities ]

    Build against capabilities instead of hardcoding bank-specific assumptions.

    List banks

02 Why Open Payments?

Integrate once. Build across banks.

The API is based on the Berlin Group NextGen specification and abstracts away the differences between individual bank APIs — so you build against one interface instead of maintaining many.

LAYER 01Your applicationprototype · product UI · agent — white labelled, you own the journeyOAuth2 · REST · X-Request-IDLAYER 02Open Payments APIconsents · account information · payments · ISO 20022 · FX · bank discoveryBerlin Group NextGenLAYER 03 — BANKS & BANKING RAILSSweden · Norway · Finland · Denmark · The Netherlandsprivate + corporate

Layer 01 — your prototype, product UI or agent. The platform is white labelled; you own the customer journey.

Layer 02 — one unified, harmonised REST API: consents, account information, payments, ISO, FX and bank discovery.

Layer 03 — supported banks across Sweden, Norway, Finland, Denmark and the Netherlands, private and corporate accounts. Berlin Group NextGen based · PSD2 scope. New banks and capabilities are added continuously.

03 API building blocks

Pick the service that fits your idea

Every entry links straight into the live Open Payments documentation. Always check the API reference for the current specification.

ASPSP Information

Discover banks and capabilities.

Account Information

Accounts, balances and transactions.

Consents

Create and manage access to account information.

Payment Initiation

Create and authorise payments.

Authorisations & Signing Baskets

Authorise and sign, including multiple payments together.

ISO Payments

Submit structured instructions, get pain.001.

FX Connect

Create FX quotes for cross-border payments.

Bankgiro Lookup (Prod Access Only)

Bankgiro-related enrichment of financial data.

Payout Service (Prod Access Only)

Payout capabilities under the paymentinitiation scope.

KYC

KYC service documented under Premium APIs.

SEPA Direct Debit (Beta)(Not available in SBX)

Direct debit flows, currently in beta.

Open the full API reference

04 Start here

Get started in 5 minutes

Do steps 1 and 2 before you arrive in Stockholm. That is the difference between debugging credentials at 09:30 and shipping a prototype by 16:00.

  1. 01

    Create your Developer Portal account

    Sign up in the Open Payments Developer Portal. For Build Day, Sandbox access is all you need — no production application required.

    Create account
  2. 02

    Create a Sandbox application

    With the Developer Portal in Sandbox mode, create an application. It gives you the credentials for the Sandbox API: a Client ID, a Client Secret and your Redirect URI. Save the secret immediately — once the dialogue is closed it cannot be retrieved again.

    Get Started guide
  3. 03

    Get your access token

    Authentication is OAuth2 (OIDC) with client credentials. Tokens are valid for one hour and carry an API scope plus a PSU context scope. All values below are placeholders.

    Access Tokens docs
    01_token.sh
    curl -X POST "https://auth.sandbox.openbankingplatform.com/connect/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "grant_type=client_credentials" \
  -d "scope=accountinformation corporate"

# response
# { "access_token": "eyJhbGciOi...", "expires_in": 3600,
#   "token_type": "Bearer", "scope": "accountinformation corporate" }
  4. 04

    Make your first API call

    Account Information is the easiest place to start: create a consent for a bank, then read accounts, balances and transactions. Every call needs a bearer token and a freshly generated GUID in X-Request-ID.

    Open API guide
    02_first_call.sh
    # List the accounts covered by an active consent (Sandbox)
curl "https://api.sandbox.openbankingplatform.com/psd2/accountinformation/v1/accounts" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "X-Request-ID: $(uuidgen)" \
  -H "X-BicFi: BANK_BICFI" \
  -H "Consent-ID: YOUR_CONSENT_ID" \
  -H "PSU-ID: PSU_ID_FOR_THE_BANK"
  5. 05

    Start building

    Now build something people actually want. Combine Open Payments with the other APIs, data sources and AI tooling available at Build Day — and ship a working prototype by 16:00.

    API reference

05 Authentication

OAuth2, in one screen

Request a token with your client_id and client_secret, grant_type=client_credentials, and a scope made of one or more API scopes plus a PSU context.

STEP 01client_id + secretgrant_type=client_credentialsPOST /tokenSTEP 02access_tokenexpires_in=3600 · scope + PSU contextBearerSTEP 03API call+ X-Request-ID: new GUID

Scopes

aspspinformation
ASPSP Information Service — discover banks and capabilities.
accountinformation
Account Information Service — accounts, balances, transactions.
paymentinitiation
Payment Initiation, ISO Payments, FX Connect, KYC, Payout Service, Bankgiro Lookup and SEPA Direct Debit.
bankgiroinformation
Combined with accountinformation for ISO enrichment of Bankgirot transactions.

PSU context

Add private for personal accounts or corporate for business accounts. Keep one active token per context — with both PSU types, that is a maximum of two tokens per hour.

Full authentication docsGood to know

Quick reference — copy-paste values

  • Sandbox AUTH_HOST

    https://auth.sandbox.openbankingplatform.com

  • Sandbox API_HOST

    https://api.sandbox.openbankingplatform.com

  • Token endpoint

    POST /connect/token

  • Grant type

    client_credentials

  • Required request ID header

    X-Request-ID

  • Contexts

    private · corporate

  • Auth

    OAuth2 / OIDC

Always check the official documentation for the current API specification — endpoints and capabilities evolve.

06 Common gotchas

Before you start debugging…

The fastest fixes we see during hack days, in the order they usually bite.

07 Inspiration

Need an idea?

Here are a few things you could build with Open Payments during Build Day.

01

CFO Copilot

Connect a company's bank accounts and turn balances and transaction data into actionable financial insights and answers.

02

Cash-flow prediction

Use transaction history to spot upcoming cash-flow problems early and help SMEs make better decisions.

03

Smart reconciliation

Match payments to invoices automatically by combining banking transactions with ERP and accounting data — Zwapgrid provides ERP connectivity at the same event.

04

Payment fraud detection

Build detection logic on top of payment context and financial data to flag suspicious supplier payments or changed payment behaviour. The detection model is yours to build — Open Payments provides the data access.

05

Intelligent accounts payable

Combine invoice information with account data and payment initiation to create a smarter, safer AP workflow.

06

SME financial health

Score financial health from real balances, transactions and payment behaviour, and explain the score clearly.

07

Embedded lending

Use account information to build richer financial context for lending or financing decisions. Froda is also participating in the event — talk to them about the lending side.

08

Agentic finance

Let an AI agent reason over financial data and assist with finance workflows. Any actual payment execution must keep proper authentication, authorisation and human safeguards in the loop.

08 Build Day

Built for Build Day

You have one day. We want you to spend it building — not fighting authentication or bank integrations.

Before the event

  • 01Create your Open Payments Developer Portal account
  • 02Create a Sandbox application
  • 03Save your Client ID, Client Secret and Redirect URI
  • 04Read the Get Started guide
  • 05Try at least one API call
  • 06Bring your questions
Create Sandbox account

During the event

Open Payments Operations and Integrations team are on site throughout the day. Ask early — a two-minute question beats two hours of solo debugging.

Venue
A House, Stadsgården 6, Slussen, Stockholm
STATUS
Submission 16:00 · Presentations 17:00 · 25 Aug 2026
Event details

Schedule

08:00Doors open, breakfast
09:00Briefing
09:30Building starts
12:00Lunch inspiration sessions
16:00Project submission deadline
17:00Presentations
19:00Jury feedback and winner selection
20:00Event ends

09 Sandbox

Your playground: Sandbox

Sandbox lets you test the API with simulated data before production. There are some limitations, but it gives a good picture of what you can build with the API.

Open Sandbox / Developer PortalSandbox credentials

Note: Sandbox credentials and behaviour differ between banks. Some banks require specific PSU identifiers in Sandbox — check the credentials page first.

Test with real banking scenarios

Open Payments supports a growing list of banks, covering private and corporate accounts. The list evolves continuously, so treat the documentation as the source of truth.

  • Sweden
  • Norway
  • Finland
  • Denmark
  • The Netherlands
See all supported banks

10 Postman

Prefer Postman?

Open Payments publishes a Postman collection with ready-made API calls, plus environment settings for Sandbox and Production. Import both, set three variables, and start experimenting.

Download Postman collectionSandbox environmentProduction environment
postman variables
# after importing the collection + sandbox environment
clientId     = YOUR_CLIENT_ID
clientSecret = YOUR_CLIENT_SECRET
redirectUri  = YOUR_REDIRECT_URI

11 Documentation

Go deeper

Every link opens the live Open Payments documentation in a new tab.

01Documentation home02Get Started03API reference04Access Tokens05Good to Know (hosts, headers)06Consent & Account Information07Payments quick start08ISO Payments09Supported Banks10Sandbox credentials11Postman collection12Changelog

12 Need help?

Stuck?

We're here to help. During Build Day the Open Payments engineering team is on site all day — bring your API questions to us.

Open documentationsupport@openpayments.io

Support channels

Create a developer account and open a support case, or check the API reference first — most Build Day blockers are a scope or a header away from being solved.

Support page
Get Sandbox Access