Choosing an Acquiring Solution

Local Acquiring

Choosing an Acquiring Solution

Choosing an acquiring solution involves two steps: first select a business solution based on your collection scenario (Dynamic Payment / Static Payment / Authorized Direct Debit), then select an integration solution based on your development investment and who provides the page (Checkout Mode / API Direct Integration / Payment Link).

Integration Guide: From Business to Integration

First choose a business solution based on your collection scenario, then, considering the payment methods, who provides the page, and the development resources you can invest, choose the appropriate integration method.

The core flow of acquiring is: the user initiates a payment → the merchant creates an order with PayCools → PayCools processes the payment → funds are settled to the merchant. Within this flow, who renders the payment page and who selects the payment method determines which integration mode the merchant uses.

Choosing a Business Solution

Business solutions are first divided into one-time acquiring and authorized direct debit based on "whether the user needs to confirm each payment individually"; one-time acquiring is further divided into Dynamic Payment and Static Payment based on "how the payment information is generated". In other words: Dynamic Payment and Static Payment are two forms of one-time acquiring, while authorized direct debit is used for recurring, automatic deduction scenarios.

Dynamic Payment

The user initiates and completes payment for each order individually. The payment information (QR code / link / bill) is bound one-to-one with the order and amount, generated in real time when the order is created, and usually has a time limit.

Suitable for: one-time purchases, game top-ups, e-commerce checkout; self-service ordering / self-service machines, bill collection, PC scan-to-pay
Supported integration methods: Checkout Mode, API Direct Integration, Payment Link
Reference: Static Payment and Dynamic Payment

Static Payment

The merchant generates reusable payment information in advance (payment code / virtual account / payment reference number) that is not bound to a specific order; the amount is entered or confirmed by the user at the time of payment.

Suitable for: offline store checkout, table / room codes, donations / public collection display; bill / virtual account payments
Supported integration methods: API Direct Integration only (static payment information such as static QR codes, bills / virtual accounts must be created via API, or operated directly in the Merchant Dashboard)
Reference: Static Payment and Dynamic Payment, Bill Payment

Authorized Direct Debit

After the user completes a single authorization, you can initiate subsequent deductions as needed within the scope of the valid authorization, without requiring the user to confirm each deduction. Each deduction is processed as an independent transaction.

Suitable for: automatic renewals, memberships / subscriptions, ride-hailing, shared mobility, frictionless payments
Supported integration methods: API Direct Integration only
Reference: Authorized Direct Debit

How to Choose a Business Solution

You can decide in the following three steps:

Is it recurring / automatic deduction? If yes (subscriptions, memberships, ride-hailing, frictionless payments, etc.), choose Authorized Direct Debit; otherwise proceed to one-time acquiring.
For one-time acquiring, does the payment information need to be reused long-term, and is the amount determined by the user? If yes (in-store payment codes, table / room codes, bill / virtual account payments, etc.), choose Static Payment;
In all other cases (each order is independent and the amount is determined at order creation), choose Dynamic Payment.

Detailed comparison of the three business solutions:

Dimension	Dynamic Payment	Static Payment	Authorized Direct Debit
Does the user need to confirm each payment	Yes	Yes	Only the first authorization; subsequent deductions require no confirmation
When payment information is generated	Generated in real time for each order	Generated in advance, reused long-term	Authorization token generated at authorization
How the amount is determined	Fixed at order creation	Entered by the user or confirmed per bill	Determined at each deduction
Whether bound to an order	One-to-one with the order	Not bound, matched by identifier	Associated with the authorization
Validity period	Yes, expires after timeout	Valid long-term	Authorization token has a validity period
Expiration handling	Cannot be paid after timeout	Continuously usable	Requires re-authorization after expiration
Typical scenarios	E-commerce, self-service ordering / machines, bill collection, PC scan-to-pay	Stores, table / donation codes, bill / virtual account payments	Subscriptions, ride-hailing, shared mobility, frictionless payments
Main integration methods	Checkout Mode, API Direct Integration, Payment Link	API Direct Integration only	API Direct Integration only

Quick selection by business scenario:

Your business scenario	Recommended business solution
Amounts differ per order and reconciliation must strictly follow orders (e-commerce, self-service machines, bill collection)	Dynamic Payment
Offline stores, long-term fixed collection, amount entered by the user	Static Payment
Bill / utility payments, collection via virtual account or payment reference number	Static Payment
Donations, table / room codes, exhibitions and other variable-amount collection	Static Payment
Memberships, subscriptions, insurance renewals and other recurring automatic deductions	Authorized Direct Debit
Ride-hailing, shared power banks, deductions based on actual usage	Authorized Direct Debit
Frictionless payments needed, reducing repeated confirmations	Authorized Direct Debit

Choosing an Integration Solution

If you choose one-time acquiring (Dynamic Payment or Static Payment), you can select the appropriate integration method based on the payment method, who provides the page, and the development resources you can invest.

Checkout Mode

Integration cost: low

You create a checkout page via API and redirect the user to the PayCools checkout page. The user selects a payment method and completes the payment on the checkout page; the payment page and subsequent flow are provided and maintained by PayCools.

You need to: call the API to create the checkout page, redirect the user to it, and receive notifications or actively query the payment result
Suitable for: those who want to reduce payment page development work and access multiple payment methods through a unified page

View integration documentation →

API Direct Integration

Integration cost: medium

After the user selects a payment method on your website or app, you call the corresponding API to create the payment, and the user proceeds directly into the payment flow of the selected method; for bank card payments, the user will enter card details on a page provided by PayCools.

You need to: develop the payment method selection page, and based on the API response for each payment method, guide the user to redirect, scan a QR code, or complete payment using bill information
Suitable for: those who want to design their own checkout page and independently control the display scope and order of payment methods

View integration documentation →

Payment Link

Integration cost: minimal

You create a payment link on the PayCools Merchant Dashboard and share it with the user via email, SMS, social media, or other customer communication channels; the user opens the link, selects a payment method, and completes the payment on the PayCools page.

You need to: create and configure payment links on the Merchant Dashboard, share the link or QR code with the user, and view transactions on the Merchant Dashboard
Suitable for: those who want to initiate remote collection via customer service, operations, or sales staff without development work

View integration documentation →

Key concept: who selects the payment method

The core difference between Checkout Mode and API Direct Integration lies in "who renders the payment page and who selects the payment method":

Dimension	Checkout Mode	Pure API Mode
API restriction	Multiple payment methods	Fixed single payment method
Final selector	User selects on the PayCools checkout page	Merchant specifies directly in the API
Response content	A checkout redirect link	Specific payment information (QR code content / WebPay link)
Checkout page	Provided and maintained by PayCools	Implemented by the merchant
Development cost	Low (no page development needed)	High (requires building your own checkout / result pages)

Comparing Integration Solutions

Evaluation dimension	Checkout Mode	API Direct Integration	Payment Link
Development effort	Medium	Medium	Minimal
Customization level	Medium	Very high	Medium
Supported payment methods	All payment methods except authorized direct debit	All payment methods	All payment methods except authorized direct debit

note

Authorized direct debit only supports API Direct Integration; Dynamic Payment can be used with Checkout Mode, API Direct Integration, or Payment Link; Static Payment (static QR codes, bills / virtual accounts) must be created via API or the Merchant Dashboard and integrated via API Direct Integration.