Balance and refund draft

01 Services and entity

This draft concerns AI API credit and cloud-service prepayment arrangements coordinated by YungeRace Limited under AICloudGate. Providers, official accounts and managed routes may have different billing methods. Prepaid credit is not a bank deposit; this website does not collect payments or manage balances.

02 Before-payment checklist

Both parties should confirm in writing the product/model, ownership, route, prepaid amount, currency, unit price, metering units, quotas, credit validity, support and refund conditions. If these are unclear, continue the inquiry rather than treating a catalog entry or chat estimate as a complete order.

03 Metering, charges and balance checks

AI may be billed by input/output tokens or actual product units; cloud charges may include compute, storage, traffic and other items. The order should specify data sources, exchange rates, settlement cycle, metering delays and balance reconciliation. This website has no customer balance console.

Agree in writing per order: bill delivery, reconciliation frequency and dispute handling.

04 Credit validity

Whether credit expires, when the period starts, extension or refund options at expiry, and notice methods are agreed in writing per order. This draft sets no default validity period, promises no perpetual validity and establishes no automatic forfeiture at expiry.

05 Cancellation before activation

Cancellation before activation, incurred provider costs, a full refund or deductions, timeframes and return channel are determined by the written order before payment. If activation status or costs are unclear, reconcile the records first.

Agree in writing per order; neither “full refund at any time” nor “all payments non-refundable” is the default.

06 Unused balances after activation

Refunds, transfers to another product or extensions for unused balances, eligibility and fees are agreed in writing per order. If reserved instances, savings plans or other committed upstream costs affect refunds, they should be disclosed and confirmed before purchase, not later used as a blanket non-refundability claim.

07 Consumed usage and billing disputes

Consumed tokens or cloud resources should be reconciled against actual usage and agreed prices. Duplicate charges, metering errors, unauthorised usage or service disputes require evidence-based review; “consumed” is not a reason to refuse corrections. Refund or adjustment conditions and dispute deadlines depend on the order and applicable requirements.

Agree in writing per order: billing evidence, dispute channels and procedures. This page sets no unconfirmed day limit for objections.

08 Upstream changes or service unavailability

Model retirement, regional restrictions, quota changes or route disruptions may affect deliverables. Substitute products, repricing, migration or refunds of unused balances should first be confirmed with the customer in writing; a different model should not be substituted automatically.

Agree in writing per order: alternatives, cost allocation, remaining credit and timeframes.

09 Abnormal or prohibited use

Security incidents, suspected abuse or provider restrictions may require suspension. Suspension, fact-finding, incurred charges and remaining balances should be reviewed under the order and applicable requirements. This draft establishes no automatic forfeiture of all balances or unlimited penalties.

Legal review and per-order agreement pending: suspension notices, investigation and cost treatment.

10 Exhaustion, alerts and overages

Metering and suspension on the actual platform may be delayed; prepayment does not automatically guarantee no overage. Low-balance alerts, automatic suspension or top-ups must be checked against product capabilities and included in the order. This marketing website does not enforce those controls.

Agree in writing per order: overage calculation, notice and payment handling.

11 Fees, currency and exchange differences

Payment providers, banks, intermediaries or upstream providers may charge fees; cross-currency settlement may create exchange differences. Cost allocation, exchange rate, return-to-source arrangements and refund currency must be agreed in writing before payment. This draft sets no universal percentage fee.

12 Request channel and timeframes

Send the order reference, amount to reconcile and issue to sales@aicloudgate.ai, or use the support channel agreed in your order. Acknowledgement, verification, refund processing and actual arrival timeframes are agreed in writing per order. Do not send bank-card information, keys or payment proofs through the public form.

13 Statutory rights and document status

This notice does not exclude rights that cannot legally be excluded. Per-order agreements must still comply with applicable requirements; a draft cannot waive mandatory obligations. Its latest update is not an effective date. Final terms remain subject to company and qualified legal review. Operator: YungeRace Limited. Contact address: UNIT A7, 12/F ASTORIA BLDG 34 ASHLEY RD TSIM SHA TSUI HONG KONG.