Balance and consumption
Prepaid balance funds future API consumption. Correctly metered completed calls are consumed services. Unsatisfactory output alone does not establish a billing error. Check order and usage records for failed calls, incorrect charges or duplicate payments.
Eligibility for refunds of unused balance, application deadlines, fees and payment restrictions still require a confirmed policy. This draft promises neither automatic refunds nor a fixed arrival time. Mandatory legal rights remain unaffected.
Missing credit and payment differences
Successful payment and credited balance are different states. Retain order identifiers, times, payment status and evidence of the actual debit. Do not pay repeatedly to refresh an order. Payment notifications, credits, duplicates, exchange rates and fees must be reconciled.
Unverified transfers or amount differences need manual review. A screenshot alone is not proof of credited balance, and credit should not be added twice without checking.
Incorrect and duplicate charges
Report failed calls with charges, duplicate settlements or incorrect metering using the local request identifier and time. The service should check records and correct confirmed errors.
A connection failure or partial response may still involve valid usage. An incomplete client response does not establish zero consumption. Balance corrections and refunds through a payment channel are distinct outcomes that should be explained.
Policy violations
Remaining balance is non-refundable when a content-policy violation causes restriction or termination. Training, distillation or extraction may cause immediate permanent termination, subject to mandatory legal exceptions.
Appeal a disputed violation through the content-policy process. Do not use new accounts, keys or payment disputes to evade restrictions. An appeal is not a promise of restoration or refund.
Submitting a request
Use the official support channel and provide account and order identifiers, payment time, the disputed amount, reasons and relevant local request identifiers. Reasonable identity verification may be needed. Never submit passwords, usable API keys or full payment credentials.
After review, the service should explain its decision, amounts, processing method and any missing evidence. Accepted refunds depend on the confirmed payment method and processor. No immediate payment or fixed business-day commitment is made without verification.
Closure and disputes
Resolve pending orders, disputes and necessary exports before closing an account. Service shutdowns or material capability changes require review of unused balance under effective terms, confirmed payment conditions and applicable law.
Disputed outcomes may be reviewed through the published appeal channel. The final policy must identify the operator, contacts, scope and effective date and receive legal review before use.
Contact and appeals
Service operator: to be confirmed.
Official contact details have not been published. Valid support, privacy and appeal channels must be provided before launch.
Back to top