X10Pay Global Payouts

International payouts built around your business

Pay contractors, sellers, creators and partners through X10Pay. Submit instructions by batch file or API and shape your payout process around your recipients’ locations and your team’s needs.

Two submission formats. Three payout options.

Who it’s for

More recipients. A clearer payout process.

01

Marketplaces and platforms

Pay sellers and service providers after orders or at the end of a reporting period. Batch files bring multiple payout instructions into one submission.

02

Businesses with distributed teams

Make regular payments to independent contractors and freelancers across countries, with submission formats and payout methods suited to your payment arrangements.

03

Creator platforms

Pay creators, streamers and other contributors: for example, their earnings for a period or rewards calculated under your platform’s terms.

04

Partner programmes and customer services

Partner commissions, referral rewards and selected customer compensation or refund use cases, subject to suitability review.

Batch files or API

Fit payouts into the way you work

01

Batch files for scheduled payouts

Compile recipients, amounts and required payment details in an agreed format. A practical choice when your finance team prepares periodic payouts together.

For example: monthly contractor payments or weekly seller settlements.

02

API for your own systems

Submit payout instructions from your product or internal system. A useful approach when payouts follow business events and manually preparing each batch becomes impractical.

For example: submitting an instruction after an order is completed or a partner commission is calculated.

Payout methods

Bank accounts, eligible cards and SBP

01

Bank accounts

Pay using a recipient’s bank details, including IBAN where applicable. IBAN identifies a bank account; it is not a separate payment network.

02

Visa Direct

Payouts to eligible Visa cards. The recipient’s card and bank are considered when assessing the payout route.

03

SBP in Russia

Payouts to individuals using a phone number and their selected bank participating in Russia’s Faster Payments System (SBP).

The payout process

From instructions to reconciliation

  1. 01

    Define your use case

    Outline countries, currencies, recipient types, payment purposes and expected volumes.

  2. 02

    Agree the setup

    Select payout methods, a batch file or API format, and instruction-processing terms.

  3. 03

    Prepare for launch

    Establish required data, submission procedures and how to handle errors or changes to recipient details.

  4. 04

    Plan reconciliation

    Before launch, agree how your team will receive results and match them against the original instructions.

Getting started

Tell us about your payouts

A short overview is enough to start the conversation. Share:

  • Destination countries and currencies
  • Who you pay and what the payments are for
  • Estimated payout count and monthly volume
  • Preferred frequency and payout methods
  • Your preferred format: batch files or API

Frequently asked questions

Do batch payouts require development work?

Batch files let you submit multiple instructions without an API integration. We agree the file format and submission method during onboarding.

What if a payout cannot be completed?

Before launch, we agree how notifications, data corrections and next steps for these instructions will be handled.

How do I find out about pricing and timing?

Share your destinations, currencies, volumes and preferred payout methods. These details form the basis for terms tailored to your use case.

Find the right payout setup for your business

Tell us who you pay, where they are and how often you pay them. Let’s discuss available destinations, onboarding and pricing.

Request your terms
Pricing and terms

Countries, currencies, payout methods, recipient types, limits, timing and pricing depend on the route, banks, payment systems and onboarding terms. Availability for your use case is confirmed before launch.