Skip to content

Finastra (Fusion Treasury)

Finastra is the third-largest fintech by revenue, dominant in European bank treasury and payments. Fusion Treasury and Fusion Payments are used by mid-to-large banks across the UK, Germany, France, Benelux, and the Nordics.

DPX integrates via FusionFabric.cloud — Finastra’s open API marketplace. DPX registers as a FusionFabric app. Banks already running Fusion Treasury install the DPX app from the marketplace. When a treasury team initiates a cross-border payment, DPX appears as an alternative settlement channel alongside SWIFT.

Fusion Treasury payment run (bank-side)
│ Cross-border payment selected for DPX routing
│ FusionFabric app call → DPX Payment International endpoint
POST https://integration.untitledfinancial.com/payments/initiate
├── Compliance Oracle (VoP, AML, sanctions)
├── Stability Oracle (macro gate)
├── ESG Oracle (SFDR PAI indicators)
└── Settlement → DPX rail (USDC / EURC on Base)
ISO 20022 pacs.002 → FusionFabric → Fusion Treasury write-back

No bank core system change required. DPX appears alongside SWIFT as a settlement option in the Fusion Treasury payment workflow.


Finastra’s FusionFabric.cloud marketplace operates differently from a direct API connection:

StepWho does itWhat happens
App registrationDPXRegister at developer.fusionfabric.cloud
App listingDPXSubmit DPX app to FusionFabric marketplace for bank discovery
App installationBankBank’s tech team installs DPX from Finastra marketplace
OAuth authorizationBankBank authorizes DPX to receive payment events from Fusion Treasury
Payment routingBank treasury teamSelects DPX as the rail for eligible cross-border payments
SettlementDPXOracle gating + on-chain settlement + pacs.002 returned

To list DPX on the FusionFabric marketplace:

  1. Register at developer.fusionfabric.cloud
  2. Create a new application under FusionCreator → My Apps → New App
  3. Subscribe to the Payment International API (payment-international-v1)
  4. Configure your OAuth redirect URI: https://integration.untitledfinancial.com/finastra/oauth/callback
  5. Submit for Finastra marketplace review

Credentials received:

CredentialWhere used
FFDC_CLIENT_IDOAuth client credentials grant
FFDC_CLIENT_SECRETOAuth client credentials grant
FFDC_TENANT_IDPer-bank identifier passed in API calls

FusionFabric uses OAuth 2.0 client credentials:

Terminal window
POST https://identity.fusionfabric.cloud/oidc/token
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials
&client_id=<FFDC_CLIENT_ID>
&client_secret=<FFDC_CLIENT_SECRET>
&scope=payment-international-v1

Token response:

{
"access_token": "eyJ...",
"token_type": "Bearer",
"expires_in": 3600
}

Include the token on all subsequent requests:

Authorization: Bearer <access_token>

1. Receive payment initiation from Fusion Treasury

Section titled “1. Receive payment initiation from Fusion Treasury”

When a bank treasury team routes a payment to DPX via FusionFabric, Finastra delivers the payment instruction to DPX’s registered webhook:

POST https://integration.untitledfinancial.com/finastra/payment-events

Payload is ISO 20022 pain.001 — same format accepted by the Integration API:

{
"paymentId": "FFDC-2026-00421",
"tenantId": "<bank-ffdc-tenant-id>",
"format": "pain.001.001.09",
"payment": {
"amount": "250000.00",
"currency": "USD",
"creditor": {
"name": "Recipient GmbH",
"lei": "529900ODI3047E2LIV03",
"iban": "DE89370400440532013000"
},
"debtor": {
"name": "Sending Bank Corp",
"lei": "7LTWFZYICNSX8D621K86"
},
"remittanceInfo": "Invoice FFDC-2026-00421"
}
}

DPX maps the Finastra payment to the Integration API and returns:

{
"dpxPaymentId": "93e89fe0-...",
"status": "SETTLED",
"settlement": {
"txHash": "0x7f3a...",
"network": "base-mainnet",
"settlementAsset": "EURC",
"amount": "250000.00",
"fee": "508.75"
},
"esg": {
"score": 74,
"sfdr": { "article8Compatible": true, "paiIndicators": { "..." } }
},
"compliance": {
"fatfR16Compliant": true,
"micaCompliant": true
},
"iso20022": {
"format": "pacs.002.001.10",
"status": "ACCP",
"payload": "<base64-encoded pacs.002>"
}
}

DPX POSTs the pacs.002 back to the bank’s FusionFabric callback URL. Fusion Treasury receives the settlement confirmation and updates the payment status in the bank’s core system.


For banks that want a direct H2H connection before the marketplace listing is live, or for private deployments:

Terminal window
POST https://integration.untitledfinancial.com/payments/initiate
Authorization: Bearer <dpx-institution-key>
Content-Type: application/json
{
"tmsReference": "FFDC-2026-00421",
"amount": "250000.00",
"currency": "USD",
"settlementAsset": "EURC",
"creditor": {
"name": "Recipient GmbH",
"lei": "529900ODI3047E2LIV03",
"walletAddress": "0x..."
},
"debtor": {
"name": "Sending Bank Corp",
"lei": "7LTWFZYICNSX8D621K86"
},
"callbackUrl": "https://bank-finastra-instance/dpx/callback"
}

Contact [email protected] to receive an institution key for direct access.


Set via wrangler secret put <NAME> in the Integration API worker:

SecretDescription
FFDC_CLIENT_IDFusionFabric OAuth client ID
FFDC_CLIENT_SECRETFusionFabric OAuth client secret
FFDC_WEBHOOK_SECRETHMAC key for verifying inbound Finastra webhook events

MarketProductCommon in
UK banksFusion Payments, Fusion TreasuryClearing banks, mid-tier
DACHFusion Corporate ChannelsCorporate banking arms
FranceFusion Trade InnovationTrade finance desks
BeneluxFusion TreasuryCorporate treasury, asset managers
NordicsFusion EssenceRetail + corporate banking

Every DPX settlement returns:

  • FATF R16 VoP — on-chain Verification of Payee
  • MiCA — settlement rail and EURC both MiCA-compliant
  • SFDR PAI — ESG block per transaction for SFDR fund-level reporting
  • AML6 — behavioural profiling + sanctions screening
  • Travel Rule — IVMS 101 records for payments ≥ €1,000 (FATF R.16 EU threshold)

DPX FusionFabric app registration is the prerequisite. Until the marketplace listing is live, direct H2H connections are available for any Finastra bank that contacts DPX directly.

Contact [email protected] or register for beta access.