1. Before paying
Use only the payment methods actually shown in your account. Check the amount, currency, credit to be received, relevant fees and purchase conditions before confirming. A payment method mentioned in software documentation is not necessarily enabled on AIAPI.
2. Usage-based charges
Requests are accounted for under the configured model and group rules. A local timeout does not prove that upstream processing stopped. Repeating a request may create additional usage. Review usage records before assuming a charge is incorrect.
A generated answer that needs editing is not, by itself, proof of a billing error. This does not exclude rights concerning defective or non-conforming service under applicable law.
3. How to request a review or refund
Email [email protected] with the subject “AIAPI — payment”. Include the account contact, payment date, amount, currency, transaction reference and a concise explanation. For disputed usage, add the request identifier and time where available. Never send a full card number or API key.
We will review the records and explain the result. Duplicate payments, technical errors, unused balance, cancellation and service-conformity issues need different checks. Eligibility, amount and timing depend on the facts, applicable rights and payment provider; no automatic “no refunds” rule is imposed here.
4. Mandatory consumer rights
Where Georgian consumer-protection law applies, mandatory information, conformity, withdrawal and remedy rights remain in force subject to the law’s conditions and exceptions. Commencing a digital service does not, by itself, establish that every withdrawal right has been validly waived.
Any legally required separate consent or acknowledgement must be obtained in the relevant purchase flow, not inferred from this policy. Contact us before paying if a purchase condition is unclear.