Website Custom Development: If a Client Wants to Collect Deposits on the Official Website, Should WeChat Pay or Alipay Be Connected First?

In custom website development, when a client wants to collect deposits on the official website, there is no single answer to whether WeChat Pay or Alipay should be connected first. Based on 2026 project delivery experience, if most customers come through WeChat shares, official accounts, or mobile devices, connecting WeChat Pay first is usually smoother; if customers are used to comparing prices on a computer and paying by corporate transfer, Alipay or bank transfer is more common. Both usually require corporate qualifications, ICP filing, and a corporate account, and personal payment codes are not suitable for long-term business collections. A more reliable approach is to first look at customer sources, device habits, order amount ranges, and qualification conditions, then decide whether to connect one channel first or both together.

Collecting Deposits on an Official Website Is Not the Same as Collecting Payments in an Online Store

Collecting deposits on an official website is usually a low-frequency, relatively large-amount, service-based transaction that requires manual confirmation. After a customer clicks “Pay Deposit,” the process still involves signing a contract, issuing an invoice, and arranging scheduling; payment is only one segment of the chain. This differs from the high-frequency, small-amount, automatic-fulfillment payment logic of e-commerce stores, so store configurations cannot be applied directly.

• Frequency: Official website deposits are commonly a few to dozens of transactions per month, while an online store may handle hundreds or thousands per day.
• Amount: Deposits commonly range from several hundred to tens of thousands of RMB (experience range), while online store order values are usually lower.
• Confirmation: Official website payments often require manual confirmation of receipt by sales or customer service, while most online store orders are fulfilled automatically.
• Refunds: Official website refunds often go through offline negotiation, while online store refunds follow a standard process.

Whether to Connect WeChat Pay or Alipay First: Look at Four Dimensions

The order of judgment is not “which one is more popular,” but where customers are, what devices they use, how large the amounts are, and how reconciliation will be handled later. Listing the four dimensions and going through them with the client item by item is more reliable than directly recommending one channel.

• Customer source: Within the WeChat ecosystem (official accounts, groups, Moments), prioritize WeChat Pay; for customers coming from Baidu, Douyin, or email, Alipay or UnionPay on PC is more common.
• Device habits: On mobile, WeChat Pay has fewer steps; on PC, Alipay QR code scanning or online banking is smoother.
• Amount range: For deposits from several hundred to several thousand RMB, both WeChat Pay and Alipay can cover them; for amounts above tens of thousands of RMB, corporate transfer still accounts for a certain proportion.
• Qualifications and accounts: Both WeChat Pay and Alipay require a corporate entity and a corporate account; the ICP filing entity is recommended to match the business license, otherwise the application is likely to be returned.

Option Comparison: WeChat Pay, Alipay, and Bank Transfer

The three methods are not mutually exclusive; a common approach is “connect one online payment method first, and keep bank transfer for the long term.” The comparison below covers suitable users, fee experience range, settlement cycle, and refund experience. Specific details are subject to the payment provider’s current policies.

• WeChat Pay: Suitable for mobile and in-WeChat orders; fees commonly around 0.6% (experience range); settlement typically T+1; refunds returning to the original route are relatively smooth.
• Alipay: Suitable for PC and customers accustomed to Alipay; fees commonly around 0.6% (experience range); settlement typically T+1; refunds return to the original route.
• Bank transfer: Suitable for large amounts and corporate payments; no channel fee but requires manual reconciliation; arrival time depends on the bank; refunds require offline operations.
• Note: Fees, settlement cycles, and limits vary by industry and merchant type. Check the payment provider’s official documentation before signing.

Delivery in Practice: Where Qualifications and APIs Commonly Get Stuck

A common situation in projects is that the client’s business department is pushing to go live and collect deposits, but finance and administration have not prepared the materials. Typical constraints include a limited budget, a delivery period of around two weeks, only a business license and legal representative ID as source materials, and compatibility with both the WeChat in-app browser and PC. The approach is to first list the qualification checklist, have the client process the corporate account and payment application in parallel, and use “offline transfer + manual confirmation” as a fallback on the front end. As a result, payment applications commonly take 1 to 3 weeks (experience range). If you wait for all APIs to be fully connected before going live, the overall schedule is likely to be delayed; going live with the fallback first means customer service must manually verify receipts in the early stage. According to delivery practice, this type of fallback is marked separately in the acceptance checklist.

• Common blocker 1: The business license’s business scope does not match the payment collection business, and the payment provider requires additional explanation.
• Common blocker 2: The ICP filing entity and the business license are inconsistent, requiring a filing change first.
• Common blocker 3: The corporate account has not been opened or has been unused for a long time, causing payment verification to fail.
• Common blocker 4: The website lacks HTTPS or the domain has no filing, so the payment API cannot complete callbacks normally.

An Actionable “Four-Layer Payment Implementation Checklist”

According to delivery practice, payment implementation is divided into four layers, checked layer by layer from qualifications to after-sales, which can reduce situations where missing materials are discovered only after launch. Each layer needs a clear “pass line,” rather than only checking whether the payment button can be clicked.

1. Qualification layer: The four items—business license, legal representative identity, ICP filing, and corporate account—have consistent entities. The pass line is passing the payment provider’s initial review.
2. Account layer: Merchant ID, API key, certificate files, and callback domain are fully configured. The pass line is that sandbox or small real payments can go through.
3. Link layer: The five-step closed loop of order placement, payment, asynchronous notification, order status write-back, and timeout closure. The pass line is that orders do not get stuck after network disconnection or payment cancellation.
4. After-sales layer: Refund entry, reconciliation files, customer service scripts, and invoice process are clear. The pass line is that finance can reconcile monthly.

The reason for this division is that qualification and account issues usually get stuck on the client side, while link and after-sales issues fall on the development side. Advancing client-side materials first while the development side builds fallback in parallel makes the overall schedule more controllable.

Common Pitfalls: Personal Payment Codes, Second Clearing, Refunds, and Reconciliation

The common pitfalls in collecting deposits on an official website are often not incorrectly written APIs, but unclear payment collection entities and fund paths. Using a personal payment code for business collections causes trouble later with invoicing, reconciliation, and refunds; if a third-party “aggregated payment” without a payment license sends funds to someone else’s account first, there may be second clearing risk. During delivery, verify the fund flow first.

• Personal payment code: Not suitable for long-term business; limits, risk control, and invoicing are all restricted.
• Second clearing risk: If funds first enter an unlicensed intermediary account and are then settled to the merchant, caution is required.
• Refunds: Returning to the original route is smoother; offline transfer refunds require keeping evidence.
• Reconciliation: Payment providers supply statements, and finance’s accounting basis should align with website order statuses.
• Asynchronous notification: Payment results should be based on the server’s asynchronous notification, not only the front-end redirect page.

Suitable Scenarios and Boundaries

Collecting deposits on an official website is suitable for businesses with clear service contracts, relatively high order values, and scheduling needs, such as custom development, decoration, consulting, and training. It is not suitable for purely informational websites, sole proprietors without a corporate account, or scenarios where each transaction is only a few dozen RMB and automatic fulfillment is expected.

• Suitable: Has corporate qualifications, a corporate account, contracts and refund processes, and a stable number of deposits each month.
• Not suitable: Purely informational website, no corporate account, extremely small single transaction amounts, no after-sales manpower.
• Online payment not necessary: The customer group consistently uses corporate transfer, and finance is already used to offline reconciliation.

Boundary statement: If you only occasionally collect one or two deposits and the client is willing to use corporate transfer, you can operate without connecting online payment first; connecting a channel after business volume stabilizes is less troublesome. When making decisions in 2026, it is advisable to judge “whether qualifications can be obtained” before “which API to connect first.”

Frequently Asked Questions

For collecting deposits on an official website, must both WeChat Pay and Alipay be connected?

Not necessarily. Connect the one channel that customers commonly use first, and keep bank transfer as a fallback; connecting both usually increases reconciliation and refund maintenance costs, so add the other based on actual order volume.

Without a corporate account, can I use a personal payment code to collect deposits on the official website?

Not recommended. Personal payment codes are restricted in limits, risk control, and invoicing. For business collections, it is advisable to apply for a payment channel as a corporate entity; otherwise, refunds and reconciliation later can easily lead to disputes.

How long does a payment API application usually take?

When materials are complete, it commonly takes 1 to 3 weeks (experience range); if the ICP filing entity or business license scope needs to be changed, the time will be significantly longer.

For collecting deposits on an official website, what are the approximate fees?

WeChat Pay and Alipay are commonly around 0.6% (experience range). Different industries and merchant types vary, so check the payment provider’s current policies before signing.

If a customer pays successfully but the website order does not change, where should I check first?

First check whether the server asynchronous notification was received and whether the callback domain is correctly configured, then check the order status write-back logic. Do not rely only on the front-end redirect page.

If you are preparing to collect deposits on an official website in 2026, first have the client confirm that the business license, ICP filing, and corporate account entities are consistent, then proceed according to the “four-layer checklist.” This is suitable for businesses with contracts, scheduling, and refund processes; if you only occasionally collect one or two payments and the client is willing to use corporate transfer, keeping offline confirmation first is less troublesome. Specific fees and limits are subject to the payment provider’s current policies.