refunds and billing disputes

01incorrect charges

confirmed duplicate or incorrect charges are corrected. a review needs the request or payment identifier, transaction time and a description of the issue. support does not require your api key or password.

02unprovided and partially delivered services

when a request was not executed, billing is reviewed against technical evidence. an interrupted stream requires a separate assessment of what was actually delivered and recorded. an HTTP error or disconnected connection alone does not establish the amount processed.

a mismatch with the advertised model or capabilities is reviewed as a service-quality dispute. dissatisfaction with an ai response’s wording alone does not mean the request was not executed; mandatory user rights remain unaffected.

03unused balance

unused deposited funds are handled through a separate refund request. the available refund method, amount, applicable fees and conversion terms are agreed before confirmation. customer refunds and seller earnings withdrawals are different operations; the seller withdrawal minimum does not set a customer refund minimum.

04review and outcome

the outcome must state the grounds and adjustment amount, or a clear reason for refusal. confirmed adjustments are recorded in settlement history rather than silently rewriting old transactions. support contacts, review timelines and available refund methods will be published before launch. mandatory legal rights and deadlines are not excluded.

05blockchain transfers

check the network, token, address and any required comment or memo before confirming a transfer. a submitted blockchain transaction generally cannot be cancelled by 2api. an incorrect destination does not excuse an error made by the service itself; causes and responsibility are reviewed separately.