01 · Global Institutional Payments Network

A modern payment network for global institutions.

XDC Payments gives banks, corporate treasuries, and payment providers a portal for payment operations, with API access for approved clients. Fast settlement, with delivery times depending on the corridor, payment method, provider availability, banking hours, and compliance checks.

Portal
Manage payments
Payments API
Connect approved software
Permissions
Assigned by capability
Eligibility
Organization and corridor
02What we offer

Payment operations, connected.

Manage payment workflows through the XDC Payments portal. Approved clients can connect their own software through the Payments API.

01

Account information and access

Account information and payment workflows are available according to your organization’s eligibility, assigned permissions, and supported corridors.

02

Cross-border payment workflows

Initiate supported payment workflows in the portal or through an approved integration. Delivery timing depends on the corridor, method, provider, banking hours, and compliance checks.

03

Pricing by corridor

Pricing depends on the selected corridor, payment method, and providers. Request current pricing for your use case before initiating a payment.

04

Compliance requirements

Verification, screening, messaging, and other controls depend on the applicable workflow, corridor, providers, and your organization’s requirements. Confirm the current scope during onboarding.

05

Payments API

Approved clients can retrieve account information and initiate supported payment workflows using customer-specific API keys. Access depends on assigned permissions and account eligibility.

03Payments API

Your payments workflow. Your interface.

Use the XDC Payments portal to manage payments, or connect your own software through the Payments API. Approved clients can retrieve account information and initiate supported payment workflows using customer-specific API keys. Access depends on assigned permissions and account eligibility.

Built for payment operations, embedded payment experiences, and treasury automation.

Permissions are separate: read access, resource management, and payment initiation are distinct permissions. Not every key has every capability.

Get started in three steps

01

Complete business verification and confirm the capabilities and corridors available to your organization.

02

Set up an authorized client administrator and API-key permissions.

03

Connect your integration, verify a first read request, and begin approved payment workflows.

04How a payment flows

From payment in to payment out.

A payment workflow may connect a sending method, settlement process, and beneficiary payment method. On-chain settlement finality is separate from beneficiary bank receipt.

Illustrative workflow only: this diagram is not a live transaction, supported-route confirmation, quote, or payment initiation. Fast settlement, with delivery times depending on the corridor, payment method, provider availability, banking hours, and compliance checks.

Payment in (example)
Settlement process (example)
Beneficiary method (example)
Example sending methodUSD
Example sending methodEUR
Example sending methodGBP
Example sending methodMXN
Example sending methodBRL
Example sending methodJPY
EXAMPLE IN EXAMPLE OUT
Settlement process (illustrative)
Process depends on approved workflow
Availability and assets depend on eligibility and provider support
EXAMPLE IN EXAMPLE OUT
Settlement finality
Separate from bank receipt
Timing varies by corridor, method, provider, banking hours, and checks
EXAMPLE
Illustrative beneficiary amount
Exampleonly
Not a live payment
— Example output
Beneficiary payment method varies by route
— API access
Supported workflow, subject to permissions and eligibility
05Example workflow

Receive. Process. Pay out.

This illustrative sequence is not a statement of live route availability, a quote, or a service-level commitment.

01 · Collect

Use an eligible sending method.

A sender uses a payment method available for the approved account and corridor. Account details, payment methods, and eligibility are confirmed during onboarding.

Example methodUSD · WIRE
AccountExample account
CorridorConfirm during onboarding
Illustrative only
02 · Process

A supported payment workflow.

The applicable workflow, providers, assets, and permissions depend on account eligibility and the selected corridor. No automatic cheapest or fastest route is represented here.

Example in
Illustrative
→ XDC →
Example out
Not a quote
Example only · no price or route implied
03 · Deliver

Settlement and bank receipt are distinct.

On-chain settlement finality does not mean the beneficiary bank has received funds. Bank receipt depends on the corridor, payment method, provider availability, banking hours, and compliance checks.

BeneficiaryExample recipient
TimingDepends on route
ReceiptNot confirmed by this diagram
Illustrative only
06Payment approaches

Compare the workflow.

A high-level comparison only. Availability, timing, pricing, providers, and processing requirements vary by corridor and payment method.

What matters
Traditional correspondent banking
XDC Payments
Timing
Depends on banks, intermediaries, payment method, and destination.
Fast settlement, with delivery times depending on the corridor, payment method, provider availability, banking hours, and compliance checks.
Operating windows
Banking and provider schedules vary.
Blockchain settlement and beneficiary bank processing are separate; bank receipt can depend on banking hours.
Pricing
Varies by bank, FX provider, and intermediaries.
Request current pricing for the selected corridor and payment method.
Funding
Funding and settlement requirements vary by provider and route.
Requirements depend on account eligibility and the approved workflow.
Payment visibility
Tracking options vary by institution and payment method.
Available account information and payment records depend on assigned permissions.
Integration
Options vary by institution and implementation.
Approved clients can connect their software through the Payments API, subject to assigned permissions.
07Platform capabilities

Designed for payment operations.

Capabilities depend on account eligibility, assigned permissions, payment method, corridor, and provider availability.

01

Settlement timing

Fast settlement, with delivery times depending on the corridor, payment method, provider availability, banking hours, and compliance checks.

02

Pricing by workflow

Pricing varies by corridor, payment method, and providers. Request current pricing for your use case.

03

Corridor-specific access

Available payment methods and account capabilities are confirmed for your organization during onboarding.

04

Business verification

Complete business verification and confirm the applicable compliance requirements for your account and workflow.

05

Account information

Approved clients can retrieve account information when their API key has the required read permissions.

06

Separate permissions

Read access, resource management, and payment initiation are distinct capabilities. Not every API key has every permission.

08Corridor examples

Illustrative payment routes.

The markets, rails, currencies, networks, and assets below are illustrative examples only—not a live availability list or confirmation that a route is supported. Confirm current capabilities for your organization during onboarding.

— Fiat in
Illustrative sending methods (not availability)
🇺🇸 US ACH / WIRE 🇪🇺 EU SEPA 🇬🇧 GB FPS 🇲🇽 MX SPEI 🇧🇷 BR PIX 🇯🇵 JP Zengin 🇸🇬 SG FAST 🇮🇳 IN IMPS 🇭🇰 HK FPS 🇦🇪 AE IPP 🇦🇺 AU NPP 🇨🇦 CA Interac
Illustrative currencies (not availability)
USDEURGBP JPYSGDHKD AEDAUDCAD MXNBRLINR
— Example network components (not Payments availability)
NATIVE XDC
— Illustrative network diagram
Example components
The diagram is illustrative only. It does not represent an active route, quote, or automatic routing decision.
Network examples · not Payments support confirmation
XDC ETHSOL AVAXBTC OPARB BASEPOLYGON TRONBNB STELLAR
Asset examples · not Payments support confirmation
USDCUSDT USDC.XDCPYUSD EURCEURS XSGDBRZ GYENHKDR
— Fiat out
Illustrative receiving methods (not availability)
🇺🇸 US ACH / WIRE 🇪🇺 EU SEPA 🇬🇧 GB FPS 🇲🇽 MX SPEI 🇧🇷 BR PIX 🇯🇵 JP Zengin 🇸🇬 SG FAST 🇮🇳 IN IMPS 🇭🇰 HK FPS 🇦🇪 AE IPP 🇦🇺 AU NPP 🇨🇦 CA Interac
Illustrative delivery examples (confirm availability)
Beneficiary bank Corporate account
Banks
Market Makers
Treasury Teams
Payment Providers
Money Movers
Fintech Platforms

Illustrative corridor explorer

Example only

Selections below only change an illustrative diagram. They do not check live route availability, return a quote, or initiate a payment.

— Example sender
— Example recipient
— Example path (illustrative)
🇺🇸 USD → Example → 🇪🇺 EUR
Illustrative only
Send rail
Example rail
Receive rail
Example rail
Example path (not availability)
USD → USDC → EURC → EUR
Timing
Varies by route

No live availability check, pricing quote, transaction status, or payment initiation is performed by this example.

09Compliance & access

Confirm the controls for your workflow.

Requirements and available controls depend on the organization, workflow, corridor, and providers. Confirm applicable details during onboarding.

01
Business verification
Complete business verification and confirm the capabilities and corridors available to your organization.
02
Assigned permissions
Read access, resource management, and payment initiation are separate permissions. Confirm which capabilities are assigned to each customer-specific API key.
03
Workflow eligibility
Account eligibility, available payment methods, and corridor support are confirmed for each organization; illustrative examples on this page are not availability commitments.
04
Compliance requirements
Confirm the verification, screening, messaging, and recordkeeping requirements that apply to your organization and each supported workflow.
10Get started

Discuss your payment workflow.

For banks, corporate treasuries, payment providers, and fintech platforms exploring payment operations or API access. Discuss account eligibility, assigned permissions, available corridors, and current pricing with the XDC Tech team.