Financial messaging
ISO 20022 API integration.
FINANCIAL MESSAGING & PAYMENTS
Explore payment integrations, digital-asset settlement and ISO 20022 financial messaging on XDC.
Bring financial institutions, businesses and digital assets into connected payment workflows. Explore the service categories below, then discuss your integration with the Payments team.
Service availability, supported markets, custody, liquidity and regulatory requirements depend on the provider and integration. Messaging compatibility does not itself certify a blockchain or guarantee settlement.
ISO 20022 API integration.
Institutional, self-custody and MPC options.
On-ramp and off-ramp integrations.
Retail, e-commerce and invoice workflows.
Domestic and cross-border settlement.
Explore the linked payments application.
Impel’s API documentation describes bank-to-bank, bank-to-corporate and corporate-to-corporate financial messaging. An institution can retain its existing settlement arrangements while using the messaging layer.
The documentation also describes optional settlement using digital assets in a message payload. Review supported assets, the integration architecture and operational requirements before choosing that path.
The published architecture separates public transaction timestamps from confidential financial-message content. Read the provider’s technical documentation for its identity, gateway, security and message-lifecycle design.
Businesses, banks, fintechs and merchants.
Cross-border transfers, domestic payments and B2B settlement.
Structured financial messages, including pain.001 and pacs.008.
They connect digital transfers with provider-supported fiat ramps.
Discuss acceptance, invoices and point-of-sale requirements.
Fees, timing, interoperability and access to ramps.
Cryptographic verification, message validation and applicable AML/KYC.
Explore trade, supply-chain and corporate-remittance workflows.
Review APIs and SDKs with the provider.
Use the original Payments enquiry form.
Read moreOpens the original form operated by Xinfin Fintech Pte Ltd.
Content carried forward from XinFin’s public website and linked primary sources. Historical material is identified where applicable.
Source record Editorial methodology