enable-banking-api

Original：🇺🇸 English

Translated

1 scriptsChecked / no sensitive code detected

Build and debug Enable Banking API integrations for account information (AIS), payment initiation (PIS), ASPSP discovery, user sessions, JWT authentication with RSA certificates, sandbox setup, and TypeScript/Node clients. Use when Codex needs to implement Enable Banking request flows, generate or validate bearer JWTs, model Enable Banking schemas, handle PSU redirect callbacks, fetch accounts/balances/transactions, create payments, or troubleshoot Enable Banking API errors.

2installs

Sourceberget1411/enable-banking-skills

Added on2026-04-25

NPX Install

npx skill4agent add berget1411/enable-banking-skills enable-banking-api

SKILL.md Content

View Translation Comparison →

Enable Banking API

Overview

Use this skill to implement Enable Banking API integrations without rediscovering the auth model, redirect flows, endpoint shapes, or common PSD2/PSU header requirements.

Workflow

Identify the requested service:
- AIS: ASPSP discovery,
```
POST /auth
```
  , redirect callback,
```
POST /sessions
```
  , account details, balances, and transactions.
- PIS: ASPSP discovery,
```
POST /payments
```
  , redirect callback, payment status, payment transaction details, optional webhooks.
- Misc:
```
GET /aspsps
```
  ,
```
GET /application
```
  , JWT generation, app registration, or error handling.
Keep private keys and generated JWTs server-side only. Never expose them in React clients, mobile apps, logs, or bundled code.
Read references/api-reference.md for endpoint paths, request/response shapes, status codes, and schema notes.
Read references/typescript-node.md when implementing a TypeScript/Node client, route handler, RPC procedure, or service-layer integration.
Use scripts/create-jwt.mjs when a deterministic local JWT is needed for manual testing or curl examples.

Core Rules

Base URL: use

https://api.enablebanking.com

. Treat

https://api.tilisy.com

as deprecated.

Auth: every API request uses
```
Authorization: Bearer <JWT>
```
.
JWT: sign with RS256 using the application private RSA key. Header must include
```
typ: "JWT"
```
,
```
alg: "RS256"
```
, and
```
kid: <application_id>
```
. Payload must include
```
iss: "enablebanking.com"
```
,
```
aud: "api.enablebanking.com"
```
,
```
iat
```
, and
```
exp
```
.
Token TTL: never exceed 86400 seconds.
Application registration: sandbox and production applications are separate. Sandbox applications are activated automatically; production requires activation/formalities and PIS requires a PISP license.
Redirect callbacks: verify
```
state
```
before exchanging codes or trusting a payment return.
AIS callback success returns a
```
code
```
query parameter; exchange it with
```
POST /sessions
```
.
PIS callback success is indicated by absence of
```
error
```
; fetch payment status before treating payment as final.
PSU headers: when an ASPSP requires PSU headers, provide all required headers or none. Partial PSU header sets can cause
```
PSU_HEADER_NOT_PROVIDED
```
.

Project Placement

When adding Enable Banking to an application:

Keep transport routes thin; place Enable Banking domain behavior in server-side service modules.
Keep secrets and server-only environment access in backend configuration. Do not put private keys or app IDs in web-visible env vars.
Keep direct database access behind repositories or data-access modules; store sessions, account mappings, and payment status through those boundaries.
Add reusable client/types near API service code unless multiple apps need direct reuse.

Local JWT Helper

Generate a bearer token for manual testing:

bash

node .agents/skills/enable-banking-api/scripts/create-jwt.mjs \
  --app-id "$ENABLE_BANKING_APP_ID" \
  --private-key ./private.key

Use

--ttl-seconds

to shorten the default 3600-second TTL.