Proposal: Reference FDC3 2.0 Settlement Adapter for InitiatePayment (ISO 20022 pacs.008 + L1 DPI)

[Synaptics-Lab]

Hi FDC3 Community,

While FDC3 2.0 standardizes the `InitiatePayment` intent and `fdc3.paymentContext` context type,

institutional desktop applications (OpenFin, Symphony, Bloomberg B-PIPE) often lack a lightweight, zero-
dependency reference bridge to translate those intents into formal ISO 20022 wires and execute atomic
settlement.

We have built and open-sourced an institutional connector under **Apache-2.0** implementing Citi's

OpenEAGO Phase 3 (Settlement Execution) and Phase 5 (Statutory Tax Remittance):

- **Zero External Dependencies:** Built with pure ESM Node 18+ (`node:https`, `node:crypto`) — runs

standalone with zero npm install supply-chain risk.
- ISO 20022 CBPR+ Engine: Generates schema-valid pacs.008.001.08 XML with dynamic SWIFT UETR
(UUIDv4) and automated 0.50% statutory Treasury Single Account (TSA) deductions.
- TypeScript Desktop Adapter: Drop-in FDC3DesktopAgentBridge routing payment contexts across red,
green, blue, and global channels.
- Live Institutional Cockpit: Deployed over Cloudflare SSL with a real-time OpenEAGO matrix,
interactive XML validator, and live L1 transaction ring at https://finos.synapticchain.xyz
- Open-Source Repository: https://github.com/Synaptics-Lab/IBM_BOB_finos_connector

### Community Question / Feedback
We would like to contribute this as an **FDC3 Documentation Recipe / Use-Case** (e.g. under `docs/use-

cases/orexamples/`) or propose it to FINOS Labs for institutions looking for an end-to-end
reference implementation of payment execution.

Would the maintainers be open to a recipe PR, or should we bring this to the next bi-weekly Standards

Working Group call for a brief 5-minute demo?

Looking forward to your guidance!

[kriswest]

Hi @Synaptics-Lab

While FDC3 2.0 standardizes the InitiatePayment intent and fdc3.paymentContext context type,

We don't currently have either that intent or context type - but will happily accept contribution of them into the Standard!

Regarding the adaptor project, I think it would make sense to bring the repo into FINOS-labs. The alternative is adding something the /toolbox folder of the FDC3 project, however, we're trying to keep that to general purpose tooling (reference implementations, the workbench, conformance testing etc.).

We would happily accept a use case contribution into the docs. We have very general use cases at: https://fdc3.finos.org/docs/next/api/spec#functional-use-cases - which doesn't feel like a fit. However, theres also a more specific set at: https://fdc3.finos.org/docs/next/use-cases/overview (see https://github.com/finos/FDC3/tree/main/website/docs/use-cases).

Also you could add an entry to the FDC3 community page for the adaptor under the tools & training section, see: https://fdc3.finos.org/community

One comment on the adaptor - I would rename FDC3DesktopAgentBridge to avoid confusion as that term has a different meaning already in the standard. See: https://fdc3.finos.org/docs/agent-bridging/spec and https://fdc3.finos.org/docs/fdc3-glossary
Perhaps FDC3PaymentsBridge or FDC3PaymentsAdaptor?

[Synaptics-Lab]

Hi team, Thank you for the fantastic response and the warm welcome! We are thrilled that you are open to these contributions and that the adaptor is a good fit for FINOS-labs. Here is our plan of action based on your recommendations: 1. **Renaming the Adaptor:** You make an excellent point regarding the naming collision. We will rename the project to **FDC3PaymentsAdaptor** to keep the namespace clear and avoid any confusion with the existing Desktop Agent Bridge terminology. 2. **Intent & Context Standards:** We will prepare and submit the PRs for the `InitiatePayment` intent and the `fdc3.paymentContext` schema for review. 3. **FINOS-labs Incubation:** We would be honored to bring the repository into FINOS-labs. Could you let us know the logistical next steps, or point us toward the onboarding documentation for initiating a repo transfer? 4. **Documentation & Community:** We are currently drafting the functional use case documentation for the adaptor and will submit it to the specific use-cases directory you linked. We will also make sure to add the tool to the FDC3 community page. We really appreciate the guidance and look forward to officially integrating this into the FINOS ecosystem. Let us know how best to proceed with the repo transfer. Best regards, Dr. Shabazz Synaptics-Lab

…

On Wed, Sep 9, 2026, 12:28 Kris West ***@***.***> wrote: Hi @Synaptics-Lab <https://github.com/Synaptics-Lab> While FDC3 2.0 standardizes the InitiatePayment intent and fdc3.paymentContext context type, We don't currently have either that intent or context type - but will happily accept contribution of them into the Standard! Regarding the adaptor project, I think it would make sense to bring the repo into FINOS-labs. The alternative is adding something the /toolbox folder of the FDC3 project, however, we're trying to keep that to general purpose tooling (reference implementations, the workbench, conformance testing etc.). We would happily accept a use case contribution into the docs. We have very general use cases at: https://fdc3.finos.org/docs/next/api/spec#functional-use-cases - which doesn't feel like a fit. However, theres also a more specific set at: https://fdc3.finos.org/docs/next/use-cases/overview (see https://github.com/finos/FDC3/tree/main/website/docs/use-cases). Also you could add an entry to the FDC3 community page for the adaptor under the tools & training section, see: https://fdc3.finos.org/community One comment on the adaptor - I would rename FDC3DesktopAgentBridge to avoid confusion as that term has a different meaning already in the standard. See: https://fdc3.finos.org/docs/agent-bridging/spec and https://fdc3.finos.org/docs/fdc3-glossary Perhaps FDC3PaymentsBridge or FDC3PaymentsAdaptor? — Reply to this email directly, view it on GitHub <#2178?email_source=notifications&email_token=CDGSHW2B27DWGAWQ4XHBVTT5OEPEBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGY2TGOJZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18365399>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CDGSHW2UIOFC6RKBWQ3YK635OEPEBAVCNFSNUABIKJSXA33TNF2G64TZHMYTEMJYGI3DSMZWHNCGS43DOVZXG2LPNY5TCMBXG43DQNJXUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CDGSHW4TB7E6ZVNDZFDQEVT5OEPEBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGY2TGOJZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CDGSHWYOG66MA3YAVHLUQ7T5OEPEBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGY2TGOJZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[kriswest]

The official FINOS documentation on how to contribute a new project can be found at: https://community.finos.org/docs/governance/Software-Projects/contribution#contribution-of-a-new-FINOS-project-or-SIG

In your contribution proposal you can draw a link to the FDC3 project - although I would suggest being clear that you will want to continue to maintain the project, alongside the FDC3 maintainers (if that is indeed what you want - you can contribute as a completely separate project if you want).

Note I'm looking forward to receiving the Intents and context contributions into FDC3. I might suggest prioritising those as we're a rapidly approaching out 3.0 release and can accept something into that release over the next couple of weeks before we vote on adoption. After that the next release will be 3.1, likely to be upto 6 months out.

There is some AI steering in the FDC3 repo to help you out with that contribution - at: https://github.com/finos/FDC3/blob/main/AGENTS.md

AI tends to find it easy to create the necessary JSON-schema defining a context - you only need to contribute the schema file and run a build. The build will take care of the rest and create docs packages, typescript files etc.. Here's an example schema: https://github.com/finos/FDC3/blob/main/packages/fdc3-context/schemas/context/order.schema.json

[Synaptics-Lab]

Hi Kris, Thank you for the guidance and the resources. We appreciate the heads-up on the 3.0 release timeline and will prioritize the `InitiatePayment` intent and `fdc3.paymentContext` contributions to ensure they make the cut. We'll also review the contribution documentation and AGENTS.md instructions to get the repo transfer and schema contributions underway. Best regards, Dr. Shabazz

…

On Thu, Sep 10, 2026, 13:13 Kris West ***@***.***> wrote: The official FINOS documentation on how to contribute a new project can be found at: https://community.finos.org/docs/governance/Software-Projects/contribution#contribution-of-a-new-FINOS-project-or-SIG In your contribution proposal you can draw a link to the FDC3 project - although I would suggest being clear that you will want to continue to maintain the project, alongside the FDC3 maintainers (if that is indeed what you want - you can contribute as a completely separate project if you want). Note I'm looking forward to receiving the Intents and context contributions into FDC3. I might suggest prioritising those as we're a rapidly approaching out 3.0 release and can accept something into that release over the next couple of weeks before we vote on adoption. After that the next release will be 3.1, likely to be upto 6 months out. There is some AI steering in the FDC3 repo to help you out with that contribution - at: https://github.com/finos/FDC3/blob/main/AGENTS.md AI tends to find it easy to create the necessary JSON-schema defining a context - you only need to contribute the schema file and run a build. The build will take care of the rest and create docs packages, typescript files etc.. Here's an example schema: https://github.com/finos/FDC3/blob/main/packages/fdc3-context/schemas/context/order.schema.json — Reply to this email directly, view it on GitHub <#2178?email_source=notifications&email_token=CDGSHW75PEMBFOKO33VLKU35OJ5DNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTHA2DGNZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18384374>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CDGSHW3AAGG2BELYKIRNTMD5OJ5DNAVCNFSNUABIKJSXA33TNF2G64TZHMYTEMJYGI3DSMZWHNCGS43DOVZXG2LPNY5TCMBXG43DQNJXUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CDGSHW4EYHATLFLEYDOXGGT5OJ5DNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTHA2DGNZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/CDGSHWYK647NWMDP6HPMADL5OJ5DNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTHA2DGNZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[Synaptics-Lab]

Hi Kris, Thank you for the clear guidance on the contribution process. We have executed the playbook exactly as outlined to hit the FDC3 3.0 window: 1. FDC3 Standard PR Submitted: We have opened PR #2204 #2204 against finos/FDC3. This PR contributes the InitiatePayment intent and the corresponding fdc3.paymentContext JSON schema (mapping to ISO 20022 pacs.008). We successfully ran the code- generation pipeline locally, so the PR includes the generated TypeScript definitions to make review as seamless as possible. 2. FINOS-Labs Incubation: Per your recommendation, we renamed the reference implementation to FDC3PaymentsAdaptor to avoid using the toolbox folder. We have prepared the repository with the necessary documentation and opened the formal incubation request at finos/community#444 finos/community#444. Let us know if you need any adjustments on the schema or intent definitions in the PR, or if you need any further technical evidence for the Labs incubation. Looking forward to seeing this land in 3.0! Best regards, Synaptics Lab

…

Message ID: ***@***.*** com>