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.
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.
Pay sellers and service providers after orders or at the end of a reporting period. Batch files bring multiple payout instructions into one submission.
Make regular payments to independent contractors and freelancers across countries, with submission formats and payout methods suited to your payment arrangements.
Pay creators, streamers and other contributors: for example, their earnings for a period or rewards calculated under your platform’s terms.
Partner commissions, referral rewards and selected customer compensation or refund use cases, subject to suitability review.
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.
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.
Pay using a recipient’s bank details, including IBAN where applicable. IBAN identifies a bank account; it is not a separate payment network.
Payouts to eligible Visa cards. The recipient’s card and bank are considered when assessing the payout route.
Payouts to individuals using a phone number and their selected bank participating in Russia’s Faster Payments System (SBP).
Outline countries, currencies, recipient types, payment purposes and expected volumes.
Select payout methods, a batch file or API format, and instruction-processing terms.
Establish required data, submission procedures and how to handle errors or changes to recipient details.
Before launch, agree how your team will receive results and match them against the original instructions.
A short overview is enough to start the conversation. Share:
Batch files let you submit multiple instructions without an API integration. We agree the file format and submission method during onboarding.
Before launch, we agree how notifications, data corrections and next steps for these instructions will be handled.
Share your destinations, currencies, volumes and preferred payout methods. These details form the basis for terms tailored to your use case.
Tell us who you pay, where they are and how often you pay them. Let’s discuss available destinations, onboarding and pricing.
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.