Refund Policy
The local build is a sandbox and does not accept real card or crypto payments. This draft explains how the current ledger and dispute paths work; production refund eligibility and timelines must be approved before collecting funds.
This dated draft records current product behavior. It must be reviewed before accepting live traffic or payments.
Pending deposits
Creating a deposit request does not credit the wallet. Funds become spendable only after a trusted confirmation or an authorized reconciliation action. An unconfirmed request can be reviewed through support.
Usage charges
Submitted SMS and connected voice usage create ledger entries. Delivery failures, routing disputes and duplicate charges should be investigated against message or call logs before an adjustment is made. A failed delivery does not automatically create a refund in this build.
Review and adjustments
A customer can raise a billing issue through the support workflow or contact form. Authorized finance or admin users can record a refund debit in the wallet ledger with a reference and the acting user ID. The current refund form does not collect a separate reason or write a distinct audit event. Any external payout remains manual and requires separate payment configuration.
Production terms pending
Before live payments, publish eligibility rules, time limits, refund destination, fee treatment and processing times for each payment method. Until then, this page is a draft operational explanation rather than a promise of a particular refund outcome.