European Institution Quickstart

This guide covers the fastest path to a working DPX integration for European institutions — banks, asset managers, insurance companies, and corporate treasuries operating under EU and UK regulatory frameworks.

---

What European institutions get from DPX

Capability	What it provides
ISO 20022 native	pain.001 in, pacs.002 out — no format translation required
EURC settlement	EUR-denominated on-chain settlement, no FX exposure for EUR flows
SFDR ESG data	PAI indicators per transaction, Article 8/9 compatibility flags
MiCA compliance	Settlement rail and asset (EURC) both MiCA-compliant
AML6 compliance	AML Oracle: sanctions screening, behavioural profiling, FATF R16 VoP
CSRD audit trail	Immutable on-chain records, external auditor verifiable
Kyriba connector	Native SPI for Kyriba-using treasury teams
SAP TRM	Direct integration via SAP Integration Suite

---

Step 1 — Run a preflight check (no auth required)

Before any setup, verify DPX is accessible and the oracle is healthy:

# Protocol manifest — capabilities, contracts, oracle status
curl https://agent.untitledfinancial.com/manifest

# Oracle health — stability score, settlement gate
curl https://stability.untitledfinancial.com/reliability

# ESG preflight for your counterparty (LEI required)
curl "https://esg.untitledfinancial.com/esg-score?lei=YOUR_COUNTERPARTY_LEI"

# Fee quote — EUR 250K, cross-border with FX
curl "https://stability.untitledfinancial.com/quote?amountUsd=250000&hasFx=true&esgScore=74"

---

Step 2 — Choose your integration path

Option A — Kyriba (recommended for treasury teams)

If your institution uses Kyriba as its TMS, DPX integrates as a certified Kyriba Connect Marketplace connector. Your treasury team initiates payments from Kyriba’s existing interface — no new systems required.

1. Submit a Kyriba SPI test payment to confirm API compatibility:

curl -X GET https://integration.untitledfinancial.com/bank-connectivity/payment-initiation/v1/banks

2. Run sandbox payment flows — see Kyriba Integration
3. Request Kyriba marketplace certification — contact DPX for the process

Option B — TIS (Treasury Intelligence Solutions)

For corporates using TIS as their payment factory — common in Germany, Netherlands, and Switzerland — DPX connects as an H2H bank endpoint. No ERP or TMS change required; your treasury team routes payments to DPX from within TIS as they would to any bank.

See TIS Integration for setup.

Option C — Finastra (Fusion Treasury)

For banks running Finastra Fusion Treasury, DPX integrates via the FusionFabric.cloud open banking marketplace. The bank’s treasury team installs the DPX app and selects DPX as the settlement channel for eligible cross-border payments — no core system change required.

See Finastra Integration for setup.

Option D — SAP TRM

For institutions running SAP Treasury & Risk Management, DPX connects via SAP Integration Suite or direct ABAP. See SAP TRM Integration.

Option E — Direct REST API (pain.001)

For any TMS or in-house system already generating ISO 20022. Note this institutional REST tier issues a Bearer-token institution key for audit and compliance attribution — this is separate from the public agent-native rail (agent.untitledfinancial.com) and oracle data (stability.untitledfinancial.com, esg.untitledfinancial.com), which remain keyless:

curl -X POST https://integration.untitledfinancial.com/payments/initiate \
  -H "Authorization: Bearer <institution-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "tmsReference":   "YOUR-REF-2026-001",
    "amount":         "250000.00",
    "currency":       "EUR",
    "settlementAsset": "EURC",
    "creditor": {
      "name":          "Recipient Entity GmbH",
      "lei":           "529900ODI3047E2LIV03",
      "walletAddress": "0x..."
    },
    "debtor": {
      "name": "Your Institution",
      "lei":  "YOUR_LEI"
    }
  }'

Option F — MCP (AI-assisted treasury)

For teams using Claude or other MCP-compatible AI assistants:

# Add to Claude Desktop config
{
  "mcpServers": {
    "dpx": {
      "command": "npx",
      "args": ["-y", "@untitledfinancial/dpx-mcp"]
    }
  }
}

Then in Claude: “Get a fee quote for EUR 250,000 cross-border settlement with LEI 529900ODI3047E2LIV03”

---

Step 3 — ESG preflight for SFDR compliance

Free PAI pre-assessment (no auth required):

GET https://compliance.untitledfinancial.com/sfdr/report?lei=529900ODI3047E2LIV03

Returns partial PAI indicators immediately — GHG, carbon footprint, biodiversity, water, waste, gender diversity. Sanctions and AML checks require the full screen.

Full ESG score + settlement params:

GET https://esg.untitledfinancial.com/esg-score?lei=529900ODI3047E2LIV03

Full response includes:

• Composite E/S/G scores
• Complete SFDR PAI indicators (GHG emissions, carbon footprint, social violations, gender diversity)
• Article 8/9 compatibility flags
• Settlement surcharge rate
• _settlement block — live fee rate, estimated saving vs SWIFT, link to execute

Store the sfdr block as a source record for your SFDR product-level PAI disclosure. See SFDR & CSRD Compliance for full field mapping.

---

Step 4 — Execute settlement

Once preflight passes and ESG data is captured:

# EUR-to-EUR (no FX fee)
POST /payments/initiate
{
  "amount": "250000.00",
  "currency": "EUR",
  "settlementAsset": "EURC",
  ...
}

# EUR-to-USD (FX fee applies)
POST /payments/initiate
{
  "amount": "250000.00",
  "currency": "EUR",
  "settlementAsset": "USDC",
  ...
}

The response includes:

• txHash — Base mainnet transaction, verifiable on Basescan
• esg block — E/S/G scores and SFDR PAI indicators at settlement time
• compliance block — FATF R16, MiCA, AML status
• pacs.002 — ISO 20022 settlement confirmation

---

Step 5 — Compliance records

For regulatory purposes, every DPX settlement produces three auditable records:

Record	How to access	Regulatory use
On-chain settlement	txHash on Basescan	External audit, proof of settlement
VoP attestation	DPXVerificationOfPayee contract on Base	FATF R16, AML6, Travel Rule
ESG at settlement time	GET /vop/history/:wallet	SFDR/CSRD PAI disclosure, CSRD audit

---

Regulatory coverage

Framework	Coverage
MiCA (EU)	Settlement rail + EURC asset — both MiCA-compliant
SFDR (EU)	PAI indicators per transaction, Article 8/9 flags
CSRD (EU)	Double materiality data, ESRS-mapped fields
AML6 (EU)	Behavioural profiling, sanctions screening, 24h cache
FATF R16	VoP on every payment — on-chain attestation
FCA (UK)	See Regulatory Positioning
Travel Rule	IVMS 101 records for payments ≥ $3,000 / €3,000

---

Sandbox environment

All endpoints are available in sandbox mode — no USDC/EURC required. Settlement calls return simulated pacs.002 confirmations with realistic data.

# Sandbox flag is set server-side — no config required
# ESG, compliance, and oracle calls are always live
# Settlement execution is simulated — in production, callers execute on-chain themselves (sender-funded model)

---

Get access

To receive an institution API key and begin integration testing:

• Apply via the beta access page
• Or request Kyriba marketplace certification directly through your Kyriba account manager

---

Further reading

• SFDR & CSRD Compliance
• EURC Settlement
• SWIFT Compatibility
• Kyriba Integration
• TIS Integration
• Finastra Integration
• SAP TRM Integration
• Regulatory Positioning