Back to Details

enable-banking-sandbox

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Enable Banking Sandbox

Enable Banking沙箱

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
.
在使用Enable Banking沙箱环境时可使用本技能。若涉及通用Enable Banking API端点、JWT签名、AIS/PIS流程实现以及TypeScript客户端模式，请使用关联项目技能
enable-banking-api
。

Workflow

工作流程

  1. Confirm the app is registered in the Enable Banking 
    SANDBOX
    environment. Sandbox and production applications are separate.
  2. Prefer the shared Enable Banking sandbox infrastructure for broad ASPSP testing.
  3. If using single-tenant TPP Infrastructure-as-a-Service, assume only Mock ASPSP is configured by default unless support has enabled more integrations.
  4. Use Mock ASPSP for stable AIS tests, custom account data, and repeatable CI/manual flows.
  5. Read references/sandbox-reference.md for sandbox limitations, Mock ASPSP behavior, and ASPSP credentials.
  6. 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.
  1. 确认应用已在Enable Banking的
    SANDBOX
    环境中注册。沙箱应用与生产应用相互独立。
  2. 优先使用共享的Enable Banking沙箱基础设施进行广泛的ASPSP测试。
  3. 若使用单租户TPP基础设施即服务（Infrastructure-as-a-Service），默认假设仅配置了Mock ASPSP，除非支持团队已启用更多集成。
  4. 使用Mock ASPSP进行稳定的AIS测试、自定义账户数据测试，以及可重复的CI/手动测试流程。
  5. 阅读references/sandbox-reference.md了解沙箱限制、Mock ASPSP行为以及ASPSP凭据信息。
  6. 将ASPSP沙箱故障视为可能与生产环境无关的问题。沙箱中断、凭据变更、重定向失败、严格速率限制、数据缺失以及过滤漏洞等情况十分常见。

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.
  • 未经验证，请勿根据沙箱行为推断真实银行的行为。
  • 不要期望Enable Banking提供大量ASPSP沙箱；许多银行的沙箱无法准确模拟生产环境流程。
  • 不要依赖所有沙箱中的日期过滤功能。Nordea和Handelsbanken是已知支持日期过滤的例外情况。
  • 在沙箱环境中使用
    GET /aspsps
    接口发现实际可用的ASPSP，以及每个ASPSP的
    sandbox.users
    、
    required_psu_headers
    、
    auth_methods
    和支付元数据。
  • 当测试需要确定性账户数据时，优先使用Mock ASPSP。Mock ASPSP不支持支付发起功能。
  • 对于Mock ASPSP的交易获取，预期会以10条为一批返回，且最新交易优先。不同ASPSP的批次大小和顺序不保证一致。

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.
在应用中实现沙箱支持时：
  • 将仅适用于沙箱的固定数据、种子辅助工具和测试凭据放在生产运行路径之外。
  • 将所选沙箱ASPSP的名称/国家以及虚假PSU ID存储在测试/开发配置中，而非面向用户的生产设置里。
  • 通过与生产环境相同的服务器端客户端路由真实的Enable Banking调用，设置
    ENABLE_BANKING_BASE_URL=https://api.enablebanking.com
    并使用沙箱应用凭据。
  • 避免前端分支对银行凭据进行特殊处理。沙箱凭据应放在开发者文档、测试或服务器端开发辅助工具中。