Custom Mini Program Development: How Much Deposit and Final Payment Should You Set to Avoid Being Cheated?

Based on project delivery practices for custom mini program development in 2026, development fees are rarely paid in one lump sum; the vast majority use installment payments. A common approach: the deposit accounts for 20%–40% of the total fee, with the final payment made after launch and acceptance, and keeping 10%–20% as the final payment is safer. To judge whether the payment schedule is reasonable, don't look at how many installments there are, but whether each payment milestone corresponds to a verifiable deliverable. Below, based on enterprise project delivery habits, we provide specific judgment methods and common pitfalls.

Why is installments more common than paying in full?

Custom development becomes harder to change as it progresses. Early requirements, prototypes, UI design, development, testing, and launch—each stage may require rework. Paying in full reduces the client's leverage in later stages, while developers worry about payment pressure. Installment payments are mainstream in mobile custom projects in 2026, with typical development cycles of 2–12 weeks and fees ranging from tens of thousands to hundreds of thousands of yuan. Staged payments are healthier. The core principle is "pay for deliverables," not "pay when the time comes."

Four-stage payment verification: what to check at each milestone?

Based on delivery practices for mobile custom development, payment can be split into four milestones, with the core being "pay for deliverables."

1. Contract deposit: 20%–40% of the total fee, used to confirm cooperation and lock in scheduling. Note that the contract should clearly state the conditions for "deposit non-refundable" and whether requirements research is included.
2. After prototype/UI confirmation: 10%–30%, provided the prototype or design mockups are confirmed by the client and recorded via email or signature.
3. Development milestone: 20%–40%, corresponding to completion of core features, with a test version or real-device demo available.
4. Launch and acceptance final payment: 10%–20%, paid after the mini program passes WeChat review, goes live, and the acceptance form is signed.

The above ratios are experience ranges, not rigid rules. Template-based mini programs may only have two installments; for fully custom projects with clear requirements, the deposit could be around 30%. The key is matching each installment's ratio to deliverables, without any "collect money but no delivery" milestones. If project requirements are unclear, the deposit can be reduced to around 20%, and the second installment can be advanced to after requirements document confirmation. The requirements document is more important than UI—it serves as both the acceptance basis and the pricing basis.

Most common payment pitfalls to avoid before signing the contract

In projects, clients often get stuck on payment details. Here are some typical pitfalls.

• Deposit above 50%: After the project starts, the developer may shelve the project midway if cash flow pressure is high, and the deposit is hard to recover.
• Vague milestones like "mid-development" or "halfway through": These cannot be verified. Change them to quantifiable conditions such as "core features completed and passing tests."
• Final payment below 10%: The developer's cooperation on acceptance fixes will decline, and small issues may be delayed.
• Payment milestones decoupled from requirements document: For example, "pay second installment on day 30 after signing"—if requirements are delayed, the client may pay for nothing.
• No clear "what if acceptance fails" clause: It's recommended to agree on the number of fix rounds and deadlines, e.g., "no more than three rounds of fixes, each within five working days."
• Payment account not a company account: This affects invoicing and future disputes. Before signing, confirm the payee is the same entity as the contract party.

In one mobile custom project we handled, the client, to meet a launch deadline, agreed to pay the second installment before prototype confirmation, when requirements were not yet frozen. We didn't insist on locking the payment milestone to requirements confirmation. As a result, requirements changed significantly, costs exceeded the budget by about 20%, and the schedule was delayed by three weeks. Based on our experience range, when payment milestones are not tied to deliverables, the probability of later disputes increases significantly.

Pay in full vs. installments: which to choose?

In 2026, installment payment is the mainstream for custom mini program development, but paying in full is not entirely impossible—it depends on budget and trust.

• Pay in full: Suitable for very small orders, such as template tweaks or logo changes worth a few thousand yuan, or with a team you've worked with multiple times. But for custom projects involving prototypes, UI, and backend interactions, paying in full carries more risk than benefit—there is little room for negotiation if requirements change repeatedly.
• Installments: Suitable for the vast majority of custom projects, with fees from 10,000 to hundreds of thousands of yuan. Common installment patterns are 30%-30%-30%-10% or 30%-20%-30%-20%, adjusted according to the project.

Based on 2026 delivery practices, for projects over 50,000 yuan, four installments are recommended; for 10,000 to 50,000, three installments are common; for under 10,000, two installments or full payment are acceptable. The dividing criterion is still "what deliverable does each payment correspond to." If the developer says full payment gets a discount, the discount is usually around 5%–10%, but if the project drags on for three months, the cost of capital tied up is far greater than the discount.

Applicability and boundaries

Installment payment is not a one-size-fits-all solution. In the following cases, you don't need complex installments: small projects with a budget below 10,000 yuan; template-based mini programs; working with a developer you've partnered with multiple times and have high mutual trust; or on-site cooperation where the developer provides source code and bills by headcount. Conversely, if it's a first-time collaboration, the project cycle is long, or requirements are not very clear, insist on detailed payment milestones, with each installment tied to an acceptable deliverable.

FAQ

Can I get a refund on the deposit?

It depends on the contract. If the developer hasn't started work, both parties can negotiate to refund a portion; if design or development has already been invested, deduct fees based on actual work done and refund the balance.

When is the final payment usually settled?

Commonly, it's settled after the mini program passes WeChat review, goes live, and passes acceptance. It's recommended that both parties sign the acceptance form, noting any remaining issues and resolution deadlines.

Do payment milestones have to be tied to the requirements document?

Strongly recommended. For example, "pay the second installment after UI confirmation" is safer than "pay the second installment 30 days after signing the contract." The requirements document is the acceptance basis, and binding payments to requirement change records reduces disputes.

What if the developer requires a deposit above 50%?

First ask for the reason. If the project has high risk or requires purchasing licensed materials, it may be acceptable to raise it, but ask for a detailed delivery plan and refund terms. If it's just "company policy," be cautious.

If the project is delayed, do I still have to pay the remaining amount on time?

It depends on the reason. If the delay is caused by the developer, the payment schedule can be adjusted per the contract; if it's due to client requirement changes, negotiate additional fees or schedule adjustment and realign payment milestones.

If you're negotiating a custom mini program development deal, first ask the other party to map payment milestones to specific deliverables and put them in the contract. Keep the deposit within 40% as much as possible, and retain at least 10% as final payment. If the other party insists on full payment or a deposit above 50% without a reasonable explanation, consider reassessing the collaboration. The above are experience ranges; adjust the exact ratios based on project complexity and mutual trust.