Proposed: FDC3 Payments Adaptor
- Dominant language
- JavaScript
- Stars
- 75
- Forks
- 40
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Description
### Contribution Prerequisites
- [x] I have read [FINOS Contribution Requirements](https://community.finos.org/docs/governance/Software-Projects/contribution-compliance-requirements).
- [x] I confirm I am contributing on behalf of a FINOS member OR I will seek a maintainer from a member during socialization.
- [x] I have reviewed the [FINOS Contribution Process](https://community.finos.org/docs/governance/Software-Projects/contribution/).
- [x] I have reviewed the [FINOS Project Lifecycle](https://community.finos.org/docs/governance/project-lifecycle) stages.
- [x] I am familiar with [FINOS Governance](https://community.finos.org/docs/governance) and [Maintainer Responsibilities](https://community.finos.org/docs/finos-maintainers-cheatsheet/).
### Target Lifecycle Stage
Labs
### FINOS Member Organization Name
Seeking sponsor during socialization (Invited to submit by Kris West, FINOS FDC3 Lead)
### Name
FDC3 Payments Adaptor
### Slug
fdc3-payments-adaptor
### Business Problem & Solution
Currently, the FDC3 standard lacks a unified mechanism to seamlessly initiate institutional payments and bridge them into DLT/blockchain
settlement networks.
This software solves that by providing the reference implementation for the `InitiatePayment` intent and `fdc3.paymentContext` (currently
proposed for FDC3 3.0 in Discussion #2178 and PR #2204). It acts as a desktop agent bridge that allows traditional financial desktop
applications (e.g., Bloomberg, Symphony, OpenFin) to trigger standard FDC3 payment intents, automatically translating them into ISO 20022 `pacs.
008` Customer Credit Transfer XML, and dispatching them to Layer-1 DLT settlement networks.
### Mission Statement
The mission of the project is to provide a standard reference implementation and adapter bridging FDC3 institutional desktop environments with
blockchain and DLT settlement networks via ISO 20022 messaging.
### Existing Materials
- **Adapter Repository (Ready for Transfer):** https://github.com/Synaptics-Lab/FDC3PaymentsAdaptor
- **Accompanying FDC3 3.0 PR:** https://github.com/finos/FDC3/pull/2204
- **Context/Discussion:** https://github.com/finos/FDC3/discussions/2178
### Additional Information (Optional)
_No response_
### Maintainer Team
| Name | Affiliation | Email | GitHub Username |
| :--- | :--- | :--- | :--- |
| Synaptics Lab | Synaptics Lab | veritasvaultone@gmail.com | @Synaptics-Lab |
### Compliance & Requirements Agreement
- [x] I understand that before being able to contribute all maintainers and contributors will need to be covered by a [Contributor License Agreement](https://community.finos.org/docs/governance/Software-Projects/contribution-compliance-requirements#contributor-license-agreement) or commits must satisfy the [Developer Certificate of Origin](https://developercertificate.org/) (DCO) requirements.
- [x] I confirm that software will be covered by the [Apache 2.0 License](https://community.finos.org/docs/governance/Software-Projects/contribution-compliance-requirements#license-information) and any [third-party code is compatible](https://community.finos.org/docs/governance/Software-Projects/contribution-compliance-requirements#third-party-code-compliance).
- [x] I have selected the appropriate [lifecycle stage](https://community.finos.org/docs/governance/project-lifecycle) based on that stage's requirements. I agree and commit to the Acceptance & Maintenance Requirements for my target stage.
### Administrative Consent & Transfer Authorization
- [x] I agree to grant 'finos-admin' Admin/Owner access to the repository for security auditing and setup.
- [x] I authorize the transfer of this code/repository to the FINOS GitHub organization upon project acceptance.
- [x] I confirm I have the legal authority (individual or corporate) to grant these permissions.
### Socialization Acknowledgement
- [x] I understand I may need to socialize this proposal to community@finos.org before a TOC review to gauge community interest.
Contributor guide
Assessment
This issue has not been assessed yet.