enable-banking-quick-start

Original：🇺🇸 English

Translated

Guide first-time Enable Banking API setup and sample flows: Control Panel signup, sandbox application registration, browser-generated private key download, RS256 JWT creation, Authorization header setup, listing ASPSPs, starting AIS authorization, exchanging callback code for a session, fetching balances and transactions, creating a SEPA payment, redirecting the PSU, and checking payment status. Use when Codex needs to onboard a developer quickly or scaffold a minimal working Enable Banking sandbox integration.

2installs

Sourceberget1411/enable-banking-skills

Added on2026-04-25

NPX Install

npx skill4agent add berget1411/enable-banking-skills enable-banking-quick-start

SKILL.md Content

View Translation Comparison →

Enable Banking Quick Start

Overview

Use this skill when a developer needs the shortest path from no Enable Banking setup to a working sandbox AIS or PIS request flow. For deeper behavior, use

enable-banking-api

,

enable-banking-control-panel

,

enable-banking-sandbox

, or

enable-banking-faq-best-practices

.

Workflow

Create or access an Enable Banking Control Panel account.
Register a sandbox application with browser-generated key unless the user already has an external key pair.
Use the downloaded private key and application UUID as JWT
```
kid
```
.
Generate a short-lived RS256 JWT and send it as
```
Authorization: Bearer <jwt>
```
.
For AIS:
- ```
GET /aspsps?country=FI
```
- ```
POST /auth
```
- redirect user to returned
```
url
```
- exchange callback
```
code
```
  with
```
POST /sessions
```
- fetch balances and transactions for an account
```
uid
```
For PIS:
- ```
POST /payments
```
- redirect user to returned
```
url
```
- fetch
```
GET /payments/{payment_id}
```
  until useful/final status
Read references/quick-start.md for runnable flow details and sample payloads.

Core Rules

Start in
```
SANDBOX
```
unless explicitly building production onboarding.
Keep the private key server-side and out of the repo.
Use
```
https://api.enablebanking.com
```
for API calls.

JWT

iss

is

enablebanking.com

; JWT

aud

is

api.enablebanking.com

.

JWT max TTL is 86400 seconds; quick-start examples should use around 3600 seconds.
Verify callback
```
state
```
before exchanging an AIS
```
code
```
or trusting a payment return.
Account
```
uid
```
values returned in
```
POST /sessions
```
are session-scoped and used for account data endpoints.
For a more robust local JWT helper, use the sibling
```
enable-banking-api
```
skill's
```
scripts/create-jwt.mjs
```
.

Project Placement

When turning quick-start code into production application code:

Put the Enable Banking HTTP client and flow orchestration in backend services.
Put secret env access in backend-only configuration.
Keep direct database persistence behind repositories or data-access modules.
Keep routes thin and use them only to start/complete flows.
Never call Enable Banking directly from browser code.