FAQs

Xe's Payments API helps businesses integrate international payment capabilities directly into their own platform. It allows you and your customers to make real-time global transactions with competitive exchange rates and reliable processing.

Yes. To make the integration process simple, we provide tools and resources such as:

1. Full API documentation with code samples
2. A sandbox environment for safe testing
3. Dedicated account manager support

To integrate Xe's Payments API, follow these four simple steps:

1. Create a Xe account and request sandbox access.
2. Use the documentation to test and integrate the API.
3. Complete verification and go live.
4. Begin processing automated global payments!

Payments API is designed to scale with your business as it grows. Whether you're a startup or an enterprise, Payments API supports high-volume transactions without sacrificing its performance.

Yes. Xe's Payments API supports invoice automation so you can create, send, process, and track invoices efficiently, all within your system.

To speak to someone about pricing, contact us to discuss how we can best assist your needs. An Xe team member will reach out to you to find the plan that aligns with your business goals. For help with integration, contact your dedicated account manager. They will be able to give you specialized help associated with setting up or any additional questions you may have.

Yes. A single contract funded in one source currency (for example, EUR) can be used to make payments to multiple recipients in different destination currencies, subject to the contract and payment configuration.

Currently, webhook functionality is not available. Payment and contract statuses can be retrieved using the API endpoints, so your application would need to query these endpoints to track status updates.

If a beneficiary's bank details change, we recommend updating the existing recipient rather than creating a new recipient record where possible. While the same beneficiary can be created multiple times, maintaining a single recipient record per beneficiary generally provides cleaner data management and reduces the risk of using outdated payment details.

Yes. Although a payment may initially show as sent, there are circumstances where it can subsequently be returned or rejected by intermediary or beneficiary banks. As webhook notifications are not currently available, you should monitor payment status via the API endpoints to identify any status changes.

At present, a Proof of Payment (PDF) is not available via the API. However, you can use the payment status endpoints to track and retrieve the current status of a payment.