enable-banking-sandbox

Original：🇺🇸 English

Translated

Test and troubleshoot Enable Banking sandbox integrations, ASPSP sandbox behavior, Mock ASPSP setup, sandbox credentials, AIS authorization simulation, transaction pagination quirks, and sandbox limitations. Use when Codex needs to choose a sandbox bank, find test credentials, explain why a sandbox ASPSP behaves differently from production, configure Mock ASPSP data, or implement project code that must work against Enable Banking sandbox environments.

2installs

Sourceberget1411/enable-banking-skills

Added on2026-04-25

NPX Install

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

SKILL.md Content

View Translation Comparison →

Enable Banking Sandbox

Overview

Use this skill when working with Enable Banking sandbox environments. For general Enable Banking API endpoints, JWT signing, AIS/PIS flow implementation, and TypeScript client patterns, use the sibling project skill

enable-banking-api

.

Workflow

Confirm the app is registered in the Enable Banking
```
SANDBOX
```
environment. Sandbox and production applications are separate.
Prefer the shared Enable Banking sandbox infrastructure for broad ASPSP testing.
If using single-tenant TPP Infrastructure-as-a-Service, assume only Mock ASPSP is configured by default unless support has enabled more integrations.
Use Mock ASPSP for stable AIS tests, custom account data, and repeatable CI/manual flows.
Read references/sandbox-reference.md for sandbox limitations, Mock ASPSP behavior, and ASPSP credentials.
Treat ASPSP sandbox failures as potentially unrelated to production. Sandbox outages, changed credentials, redirect failures, hard rate limits, missing data, and filtering gaps are common.

Core Rules

Do not infer live-bank behavior from sandbox behavior without verification.
Do not expect Enable Banking to expose many ASPSP sandboxes; many bank sandboxes do not accurately simulate live flows.
Do not rely on date filtering in all sandboxes. Nordea and Handelsbanken are known exceptions that support filtering by date.
Use
```
GET /aspsps
```
in sandbox to discover actual available ASPSPs and each ASPSP's
```
sandbox.users
```
,
```
required_psu_headers
```
,
```
auth_methods
```
, and payment metadata.
Prefer Mock ASPSP when tests require deterministic account data. Mock ASPSP does not provide payment initiation.
For Mock ASPSP transaction fetches, expect batches of 10 with more recent transactions first. Batch size and order are not guaranteed across ASPSPs.

Project Placement

When implementing sandbox support in an application:

Keep sandbox-only fixtures, seed helpers, and test credentials out of production runtime paths.
Store selected sandbox ASPSP names/countries and fake PSU IDs in test/dev configuration, not user-facing production settings.
Route real Enable Banking calls through the same server-side client used for production, with
```
ENABLE_BANKING_BASE_URL=https://api.enablebanking.com
```
and sandbox application credentials.
Avoid frontend branches that special-case bank credentials. Sandbox credentials belong in developer docs, tests, or server-side dev helpers.