A versioned record of what we explain.
Documentation changes and review dates are independent from application releases.
Edition 1.3 · Business cases and measurable pilots
Adds seven proposed collaboration cases spanning financial providers, accounting/software, distribution/enterprise and institutional relationships. Each defines contributions, a scoped pilot and measurement definitions. A shared pilot charter covers the baseline, costs, decision owners and exit. Stronger bilingual introductions lead with the customer opportunity.
Edition 1.0 · 11 October 2026
Initial partner evaluation guide: product boundaries, five partner models, architecture, payment lifecycle, money and ledger conventions, reconciliation, integration concepts, environment separation, security/data boundaries, capability map and access/evaluation checklists.
This edition reconciles newer source foundations with older status descriptions and explicitly separates source implementation from deployed behavior and financial approval. It introduces no provider activation or application access grant.
Edition 1.2 · Runnable evaluation and evidence workflow
Adds selected OpenAPI, Postman, JavaScript/TypeScript evaluation SDK, an in-memory loopback sandbox and bilingual blank enterprise review worksheets. Private evidence validation and local measurements support review without certifying external approvals or production readiness.
Edition 1.1 · Enterprise evaluation
Adds ten enterprise workstreams: multi-team review, selected API catalog and payment shapes, identity/permissions, acceptance cases, operations/support, assurance, data lifecycle, commercial governance and launch evidence. Provides bilingual downloadable enterprise packs and a selected JSON data-shape snapshot. Missing operational/legal/independent evidence stays explicitly open.
Review when the contract changes.
Update affected pages when authority, contracts, capability evidence or access policy changes. Documentation examples are versioned explanations; they do not establish an API compatibility commitment. A supported partner API needs its own explicit version and deprecation policy.
A documentation update is not a release announcement. Confirm the selected deployment and program-specific approval before relying on newly described capabilities.