Finance & budgeting
Indie Payment Launch Checklist: Compliance Before Conversion
Before money can come in, answer entity, tax, refunds and reconciliation. If you cannot, do not start selling.
Payments are not a button; they are a chain from order to reconciliation. This list puts compliance and reconciliation before conversion: confirm you can invoice, refund and reconcile, then optimize checkout conversion.
Shortlist（6）
- 独立开发者收款上线清单 ¥9.9
Lists the materials and processes required before collecting money, avoiding patchwork while selling.
- polar · 深度导读卡 ¥3.9Apache-2.0 · Python · ★10.5k
Payment and subscription abstraction for digital goods, useful when weighing merchant accounts against platform collection.
- create-ai-saas-starter · 深度导读卡 ¥4.9MIT · JavaScript
A starter template with subscriptions and quota control, clarifying which layer should own billing events.
- kimai · 深度导读卡 ¥3.9AGPL-3.0 · PHP · ★5.1k
Time and project billing for service deliveries charged by the hour.
- bigcapital · 技术雷达卡 ¥3.9AGPL-3.0 · TypeScript · ★4.1k
Accounting structure reference for separating revenue, refunds and fees into accounts.
- fail2ban · 深度导读卡 ¥4.9NOASSERTION · Python · ★18.9k
Once a payment system is public, credential brute force is the first risk; add baseline protection.
Four questions to answer first
Who is the merchant of record, how are invoices issued, where is the refund policy, and which timestamp defines reconciliation? Do not connect a live channel before these have written answers.
Callbacks are not the whole story
Async callbacks can be delayed or lost, so you need active queries and a manual reconciliation path. Fulfilment should require verified signature, matching amount and idempotent write.
Small amount first, then scale
Run the full order, pay, callback, fulfil, refund chain at the smallest amount before opening high-priced items. Skipping this usually costs one real customer complaint.
Common pitfalls
Common traps: treating the return page as success, comparing amounts as floats, non-idempotent callbacks, keys in the frontend, and refunds by hand-editing the database.
Alternatives
At very low volume, platform collection plus manual reconciliation is acceptable; past a hundred orders a day, building reconciliation and refund flows quickly pays off.