Payments API

Connect your organization's software to XDC Payments to read account information and, where separately authorized, use supported payment operations.

Access and permissions

Use explicit business API membership and separate read, resource-management and payment permissions to control access. A listed endpoint is not authorization to use it.

Before you connect

Your organization must complete KYB approval and the applicable route-activation requirements. API access uses your organization's existing payments relationship; it does not bypass verification or create a separate account. Confirm your invited payments portal account shows the correct organization.

Choose the service that will make requests and the person authorized to manage its credentials. Start with the read-first quickstart, then review the operations your integration actually needs.

Base URL

https://api.xdc.tech/v1

This is the production address. No sandbox or live request console is provided by these documentation pages.

Detail	Value
Authentication	X-Api-Key request header over HTTPS
Public reachability check	GET /health — no key required
First authenticated checks	GET /me, then GET /wallets
Download	Client Postman collection
Endpoint coverage	27 source-derived requests

Authentication

Send the API key in the header, never in the URL. It is a server credential, separate from your portal password or one-time sign-in code.

X-Api-Key: YOUR_API_KEY

Store keys in your organization's secrets manager. Keep them out of browser code, repositories, shared Postman workspaces, screenshots, and logs. See credentials and access for key creation, permissions and replacement.

Verification and limits

The October 12 deployment passed 26 public checks covering synthetic authenticated reads, permission denials, portal identity lookup and revoked-key rejection. No real payments were initiated. These checks do not establish every endpoint's payload contract, bank delivery time or continuous availability.

The production address is not a sandbox. No webhook, idempotency or rate-limit contract is promised here. Payment-capable integrations may have read plus payment permission; first connection checks should still use reads. See permissions for operations that also need resource-management access.

Integration path

1. Confirm organization eligibility and API activation with XDC Tech.
2. Make the three starter requests individually.
3. Review endpoint coverage and the fields shown in the client collection.
4. Agree payment permissions, approval requirements, and failure-handling behavior before enabling any write operation.

If a payment request times out, establish its actual status and the endpoint's verified retry behavior before resubmitting it. A successful response alone does not prove final settlement.

Get help

Contact your named XDC Tech representative during onboarding, or email support@xdc.tech. Include the HTTP method and endpoint, approximate time and timezone, status code, and sanitized error text. Include a request identifier if one was returned. Never include secrets or unredacted customer responses.