Popular starting points

Loading the full XDC search index…

Developer hubBuild · PageFrom your first contract to your next application.Wallets & custodyDiscover · PageUnderstand the network. Find your place in it.Get XDCDiscover · PageUnderstand the network. Find your place in it.Run a nodeBuild · PageFrom your first contract to your next application.Ecosystem applicationsDiscover · PageUnderstand the network. Find your place in it.Post-quantum initiativeResearch · PageA clear view of the engineering ahead.
↑ ↓ to selectEnter to openEsc to close
Browse all resources →

FINANCIAL MESSAGING & PAYMENTS

XDC Payments

Explore payment integrations, digital-asset settlement and ISO 20022 financial messaging on XDC.

On this page

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.

Explore the offering

Discuss your requirements

10 entries

Domestic and international settlement

SWIFT-related integration requirements

Liquidity arrangements

Security and compliance controls

Deferred-payment schedules

Scalability

Operating costs and margins

Small-value payments

Existing-system integration

ISO 20022 and electronic trade records

Messaging and settlement are separate choices

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.

Common questions

Who is this for?

Businesses, banks, fintechs and merchants.

Which payment flows are covered?

Cross-border transfers, domestic payments and B2B settlement.

What does ISO 20022 add?

Structured financial messages, including pain.001 and pacs.008.

How do stablecoins fit?

They connect digital transfers with provider-supported fiat ramps.

Can merchants integrate?

Discuss acceptance, invoices and point-of-sale requirements.

What benefits should I evaluate?

Fees, timing, interoperability and access to ramps.

Which controls matter?

Cryptographic verification, message validation and applicable AML/KYC.

Can this support business payments?

Explore trade, supply-chain and corporate-remittance workflows.

How does integration begin?

Review APIs and SDKs with the provider.

Who can help?

Use the original Payments enquiry form.

Read more

Connect with XDC Payments

SOURCE & CONTEXT

Content carried forward from XinFin’s public website and linked primary sources. Historical material is identified where applicable.

Last reviewed:

Source record Editorial methodology