FPSF-SS-001 — Governance
Layer: Governance · Audience: contributors, operators, compliance reviewers
Versioning Policy
This specification follows Semantic Versioning 2.0.0.
| Segment | Increment when... |
|---|---|
| MAJOR | Breaking change to any interface, data encoding, security model, fee model structure, or conformance requirement. Implementers of a previous MAJOR version MUST re-evaluate conformance. |
| MINOR | New components, flows, or requirements added without breaking existing conformant implementations. A companion specification publication is a MINOR increment. |
| PATCH | Editorial corrections, clarifications, and non-normative changes. Conformance is unaffected. |
Changes of MAJOR version require a documented rationale, a minimum 30-day community review period, and a migration guide.
Companion Specifications
| Spec ID | Subject | Status |
|---|---|---|
| FPSF-SS-002 | wallet-gateway Interface | Draft |
| FPSF-SS-003 | Checkout Engine API | Planned |
| FPSF-SS-004 | Broadcast Layer Protocol | Planned |
| FPSF-SS-005 | Client Wallet Certification | Planned |
All companion specifications MUST declare the FPSF-SS-001 version they conform to.
Contributing
The Foundation welcomes contributions from financial institutions, fintech developers, EVM engineers, security auditors, and regulators.
- Specification repository: https://github.com/fabric-payment-standards/specs
- Community: https://discord.com/invite/fabric-payment-standards
- Contact: specs@fabricpaymentstandards.org
Changelog
| Version | Date | Summary |
|---|---|---|
| 1.0.0 | 2026-03-25 | Initial release. Adopts FPSF-CPD-001 v1.0.0. Introduces per-token fee model (baseFeeAmount + operatorFeeBps per token, acquiringFeeBps per acquirer per token). Separates orderReference and acquirerId into independent bytes16 parameters throughout. Defines the full system architecture, Settlement Contract interface, validation rules, end-to-end payment flow, and security model. |
FPSF-SS-001 v1.0.0 · Draft · Fabric Payment Standards Foundation · Apache-2.0