After the service is activated, merchants can initiate batch payment requests to multiple collection accounts through the merchant platform.

Application Conditions

1. The merchant has activated the disbursement service;
2. The merchant's [Account] - [Currency Balance] has sufficient available balance;
3. If the merchant's available balance is insufficient【How to Check the Available Balance】,please refer to the [Merchant Top up Process.pdf] or 【Settlement to Top-Up Operation Process】
4. Top-Up Process & Settlement to Top-up Process Scenarios:：

Procedures

How to initiate a batch disbursement:

1. After entering the merchant platform, enter the [Disbursement] - [Batch Disbursement] page, click the [Create] button, view the template, select the country and payment method to be paid, and select the currency to be debited, and download the disbursement template.

2. Fill in the payment elements according to the disbursement template, which we have pre-filled for you with default values, noting that
   Pink cells: Required, please be sure to make changes according to the actual situations;
   Green cells: Optional, you can choose whether to fill in.
   Blank cells: Leave blank, you do not need to fill in this information.
   Amount/Currency specification:
   tradeAmount/Currency: The amount the merchant wants to pay.
   sourceAccount: SourceAccount is the deduction currency specified by the merchant(source of payment funds).

3. Upload the platform for performing basic format checks to block orders with incorrect formats, duplicate order numbers or empty required cells.

4. Get the validation results, download the part of the invalid items that failed the validation, modify it offline, and re-upload the batch.

5. Submit orders that have passed the basic format check; (if the merchant has set up a disbursement approval on the platform, the orders will enter the payment process after passing the approval)

6. Get the disbursement results (for orders requiring additional documents, online submissions can be made on the platform)

Status Description:

• Completed: All single orders in the batch have reached their final status: Success/Failure/Bounce Back;
• Processing: There are orders within the batch that have not yet reached their final status.

Authorization specification

Authorizations for batch payment operations are divided into 3 types.

• [Batch Payment]: payment order inquiry authorization.
• [Payment Application]: Batch payment application authorization, if this authorization is required, then [Batch Payment] authorization must be opened at the same time to take effect.
• [Disbursement Approval]: For merchants who have opened disbursement approval, this authorization can be given to the corresponding operator to review each disbursement order, and only those orders that have passed the review will enter the disbursement process.

Appendix

Disbursement templete specification

Field specification

• country: the country in which the merchant wants to pay (the user's country).
• method: the method by which the user will receive the payment, same as the [payment method] field on the page.
• sourceAccount: the currency of the debit account
• orderId: The order number defined on the merchant side, which cannot be repeated within the same batch and cannot be duplicated with previous order Id
• tradeAmount/Currency: The transaction tag amount and currency.
• targetOrg: The target organization of the payment, i.e. the way the user receives the funds, the specific bank/carrier that needs to make the payment, for some payment methods such as BankTransfer and CarrierBilling, the targetOrg needs to be filled in, the content of the filling is shown in the disbursement template named [targetOrg] downloaded from the platform.
• bankcode: For some banks that use the standard clearing system, the bankcode is required.
• payeeDocumentType/payeeDocumentId/payeeAccountType: Some payment methods involve fields of this type, which can be found in the sheet named [other completion specifications] in the disbursement template downloaded from the platform.
• purpose: Transaction purpose, optional, if passed, we will check. The purpose code needs to be included in the purpose list. If not, the transaction will be rejected;【purpose enumerate】
• Other fields: Cover information about the payee, such as payee account number, name, mobile phone number, address, email address, notes, etc.; see the specific payment template tips for details of the mandatory requirements for selecting this type of information in each payment method.

Amount/Currency specification

• tradeAmount/Currency: The amount/currency in which the merchant wishes to pay.
• sourceAccount (debit currency/amount): The debit currency account specified for the merchant (the source of funds for the payment).
• destinationAmount/Currency: The actual currency/amount received by the recipient, calculated from the transaction amount.

Description of scenarios for additional materials

Based on the requirements of risk control compliance, some orders require merchants to submit supplementary materials to facilitate smooth transactions, such as single payment amounts exceeding certain thresholds or payees at risk. PayerMax will send email reminders to merchants, who can log in to the PayerMax merchant platform to provide additional materials or respond via email.