Fees, balances, and settlement
Track funds by application and currency. Use the Business API for balance and release-stage reporting, and Console to manage settlement requests and beneficiary details.
Read the balance
curl --fail-with-body --get "$BUSINESS_API_BASE/balances" \
--header "Authorization: Bearer $BUSINESS_API_KEY" \
--data-urlencode "app_id=$PAYMENT_APP_ID"
The response separates available funds, locked earnings, reserve, refund and settlement commitments, risk holds, and debt. settlement_eligible_amount_minor reports the amount eligible under the applicable policy. Check as_of before using a reporting figure in your interface.
Do not sum every balance field into a total: some fields describe restrictions or commitments within the underlying balance. Display each with its meaning, application, and currency.
Understand the default release schedule
The target default revenue share is 70% for the developer and 30% for the platform. A customer's approved policy can override that split. The original transaction's policy snapshot controls its calculation.
Under the default schedule, the developer share releases in three stages, subject to eligibility checks:
| After payment | Portion of the original developer share | CNY 100 payment / CNY 70 developer share |
|---|---|---|
| 30 days | 40% | CNY 28 |
| 60 days | 40% | CNY 28 |
| 210 days | 20% | CNY 14 |
The final 20% is the reserve portion of that share. Each percentage uses the original developer share as its base. Refunds, commitments, and justified risk holds affect what can actually be released.
Use GET /release-stages to inspect scheduled amounts, released or consumed amounts, due dates, and blocked reasons. A release makes funds available under policy; it does not submit a bank settlement.
How a refund affects your share
The target default policy assigns the original payment fee attributable to a refund to the developer. The default rate used for this allocation is 2%. This is a platform accounting policy, not a statement about every provider's contracted rate.
For a CNY 100 payment under the default 70/30 split, with a CNY 2 original payment fee:
| Step | Effect |
|---|---|
| Payment | Developer share is CNY 70. The platform bears the original CNY 2 fee within its share. |
| Full refund | Customer receives CNY 100. The developer's CNY 70 share is reversed and the original CNY 2 fee is allocated to the developer. |
| Final result | Developer bears CNY 2 of original fees. No second CNY 2 provider fee is created. |
If the developer has already borne the same fee, the calculation credits that amount before applying any additional adjustment. Partial refunds use cumulative successful principal to allocate rounding differences. Three refunds of CNY 33.33, 33.33, and 33.34 allocate CNY 0.67, 0.66, and 0.67 respectively under the default 2% policy.
Read economics.actual.developer_refund_cost_minor for the confirmed impact. Its outstanding_debt_minor is a snapshot at calculated_at; use Balance for current debt.
Request a settlement
In Console, review your application balance, select the approved beneficiary, and submit a settlement request. The target product uses manual requests and USD bank transfers. Beneficiary management and settlement submission are Console workflows.
The default minimum is USD 100 of settlement principal before bank charges; approved account-closure residual payments can be exempt. The target processing policy allows two business days for review after complete materials and eligibility, then five business days after approval to submit to the bank. These intervals do not specify the receiving bank's arrival time.
For CNY-funded settlements, the final exchange rate comes from the actual bank transaction. An estimate shown before transfer is not the executed rate. For USD-funded settlements, there is no CNY-to-USD conversion to report.
Actual intermediary and receiving-bank charges are shared 50/50 under the default policy. Extra charges caused by an error follow responsibility for that error. If the bank deducts the full shared charge from the recipient, the platform's share is credited to the relevant application balance for a later requested settlement.
All amounts, rates, and timing defaults on this page are subject to the applicable versioned customer policy. Use Console records and policy snapshots to reconcile an individual transaction.