Partner commissions
Align calculated commissions with beneficiary details and track each payment by its merchant order reference.
PLATFORM PAYOUT · PARTNER SETTLEMENTS
Many settlements. Clarity on every one.
Turn commission, service-fee and contractor settlement lists into traceable payment orders that operations and finance can follow together.
ILLUSTRATION · NOT LIVE DATA
One list. Individual progress.
Illustrative settlement list · not real orders
Sample payment list01—03
- 01CommissionPAY—0012,400 USDCompleted
- 02Service feePAY—002850 USDProcessing
- 03Contractor feePAY—0031,200 USDTo review
A submission method that fits
IN PRACTICE
From a settlement list to traceable orders.
Service and contractor fees
Prepare contracts, purposes and beneficiary details based on the actual business relationship.
A submission method that fits
Import batches through the console, or create individual orders through the API and follow each result.
THE WORKFLOW
Prepare together. Confirm individually.
Submitting a list does not mean every payment completes together. Each order needs its own status tracking.
- 01
Finalise the list
Confirm the basis, amount and currency of each settlement; remove duplicates and unapproved items.
- 02
Validate beneficiaries
Check beneficiary and banking fields against the destination and payment product.
- 03
Create payment orders
Use console batch import or individual API calls, retaining each merchant order reference.
- 04
Follow individual results
Separate completed, processing and follow-up items rather than treating the entire list as one status.
BEFORE YOU START
A better list starts before submission.
These checks reduce the work of investigating individual settlements later.
Discuss your needs- 01
Traceable settlement evidence
Keep commission calculations, service contracts or fee details associated with each beneficiary.
- 02
Consistent beneficiary data
Verify names, accounts, regions and currencies, using the fields required for each method.
- 03
Exception ownership
Assign ownership for corrections, status queries and business updates to avoid duplicate actions.
FAQ
Questions, answered
Practical details about availability, activation and daily use.
Is batch import a single batch API request?
No. The console supports batch import, while the public payment API creates one order per request. Plan these two workflows separately.
Does one exception determine the whole list’s status?
Review each order’s actual status and requirements. A batch summary alone cannot establish whether a particular payment is complete or safe to retry.
How can we avoid duplicate payments?
Keep a unique mapping between internal settlements and merchant order references. Query uncertain orders before deciding on further action.
Make your business needs the next step.
Tell us your regions, currencies and payment flows to find the appropriate services and integration approach.