Choose a payment plan

Local Payments

Choose a payment plan

Choosing a payment plan is a two-step process: first, select the type of account you want to receive payments from Business Scenarios(Pay to bank account/Pay to wallet), then select based on payment frequency, number of orders and development resources Integration Scenarios(Merchant Platform Payment/API Payment).

1

Access Guidelines: From Business to Integration

The core link for local payments is: Merchants initiate payment requests → PayCools accepts and → submits payment amounts and fees deducted from the merchant balance to the local → channel to process the payment → PayCools synchronizes the results to the merchant.

On this link, selecting a payment plan is a two-step process:

Step	Select by	Optional
Step 1: Choose a business plan	Recipient's account type	Pay to bank account/Pay to wallet
Step 2: Select Integration Scenario	Frequency of payments, volume of orders, need for manual review, development resources available	Merchant Platform Payments/API Payments

In short, Who initiates the payment and whether it is processed automaticallydetermines which integration scheme is selected: ** Merchant platform paymentis initiated manually on the merchant platform; ** API payment is automatically initiated by the business system.

2

Select Business Plan

Local payments are categorized by the recipient's account type Pay to bank account And Pay to wallet Two business scenarios. Both plans use the same payment interface and order processing process.

01

Pay to bank account

In local fiat currency, to the payee Local bank account Payment.

• Applicable: User withdrawals, vendor payments, commission payouts, etc. Scenarios that require payment to a personal or business bank account
• Required: Bank, bank account and payee name (Name is recorded only, not verified)
• payMethodCode：BANK

02

Pay to wallet

In local fiat currency, to the payee Local eWallet Payment.

• Applicable: scenarios where the user needs to pay the wallet user, such as withdrawal, commission payment, etc.
• Required: wallet, wallet account/phone number and payee name (Name is recorded only, not verified)
• payMethodCode：EWALLET

How to choose a business plan

Most scenarios can be determined by the recipient's account type; some countries have dedicated channels. When initiating a payment via payMethodCode Specify the channel type via transferCode Specify a specific payout channel (country supported wallets and banks are available in country payment methods).

Beneficiary Account/Scenario	payMethodCode	Description
Local bank account	BANK	Banking channels for most countries
Local eWallet	EWALLET	Wallet channels for most countries
Thailand: Get paid with your phone/ID number	PROMPTPAY	PromptPay for Thailand only
Mexico: Getting paid with your CLABE account	CLABE	Bank CLABE channel for Mexico only
Colombia: Bre-B payouts	BRE_B	Bre-B channel for Colombia only

note

Please refer to Payout Methods by Country and API Documentation for required parameters for specific supported wallets and banks and locations.

3

Select Integration Scenario

01

Merchant platform payment

Integration costs: Very low

No technical integration required. Log in to the merchant platform to create a payment order and initiate payments to one or more recipients.

• Supports single payment: Fill in the payout information and payment amount on the platform to initiate payment to a single payee, suitable for temporary payments, small payments, and scenarios that require manual confirmation
• Support bulk payments: Reduce duplication by uploading files and creating multiple payments at once
• Large payments are supported: A large payee needs to be added and approved before it can be initiated with the payee
• No need to develop access: Available as soon as the ability to pay is activated

View integration documentation →

02

API Payment

Integration Cost: Medium

Integrate payment capabilities into your business systems, which automatically initiate single or bulk payments based on business processes.

• Automated Processing: The system can automatically create payment orders based on the order status, reducing manual operations
• Adapting to high-frequency services: Suitable for high payment frequency and large order volume scenarios
• Automatic synchronization of results: Get payment results through the asynchronous callback notification and query interface to facilitate reconciliation with your own system

View integration documentation →

4

Compare Integration Scenarios

Evaluation dimension	Merchant platform payment	API Payment
Development effort	🟢 Very low	🟡 Medium
Initiation method	Manually created in merchant platform	Automatically initiated by the business system call interface
Bulk Capability	Support bulk payments (file upload)	Support batch payment order interface
Result Acquisition	Merchant platform to view results and export records	Asynchronous callback notification + query interface
Applicable scenarios	Manual, low-frequency, or low-volume payments; large payments subject to review	High-frequency, high-volume, automated scenarios that need to be connected to business systems

note

The two schemes can be combined: for example, after initiating payments in batches through the API, the results can be reviewed and viewed on the merchant platform; or the payment can be created on the merchant platform, and then checked with its own system through the query interface.