Pay as you go.
Stay in control.
Review environment
This version is for review. Test and promotional credits are separate from purchased credits. Sandbox payments take no real money and credit only the test ledger. The owner has selected the displayed top-up prices and usage multiplier. Exchange-rate and VAT assumptions remain under review. Owner-only Bob Pay testing takes real rands and funds a separate purchased-credit balance; no test credits become purchased credits. Public retail checkout is not open.
What app tokens mean
App tokens are internal prepaid service credits, not cryptocurrency, deposits, cash, transferable assets, or a one-for-one equivalent of OpenAI input/output tokens. V1 introduces no compulsory subscription, recurring payment or token expiry. Larger top-ups grant more credits per rand; credits combine in one balance and do not create an account pricing tier. Published rand usage rates use the reference top-up; your effective rand cost depends on your package. Completed and pending purchases retain their original credit amounts; changing an offer does not retroactively add credits. Refunds and reversals use the original purchase amounts. VAT, the exchange-rate policy and full retail activation need owner review.
Costs and spending limits
Send starts your request without a separate cost-confirmation screen. Chatify computes an estimate and maximum reservation, including supplied history and enabled memories. Models and images have different costs. Set an optional maximum credits per message in User settings; otherwise available credits and system limits apply. Reasoning is included in provider output totals and is never counted twice. Automatic semantic compaction is included in the estimate and reservation. Its confirmed usage and the reply are charged together using their own model rates, with overhead applied once. Local extractive context, retrieval and manual memory processing use the configured overhead. Optional public web lookup adds its actual lookup tokens and configurable search-action fee, followed by the separate reply's processing. Open/find actions have no separate search fee. Search-result input is already included in the lookup receipt and is not charged twice there. Notes carried to the reply incur normal reply input processing. Compaction, lookup and reply share one request overhead. The question supplies public search terms automatically, with lookup context in Web activity. Send authorizes the lookup and maximum reservation under your configured limits. There is no automatic memory extraction or unapproved background AI inference. PDF export adds no provider call or AI usage charge.
The maximum cost is reserved first. Actual reported billable usage is settled against the saved pricing version, then the unused reservation is released. Internally credits retain eight decimal places. Small charges are not repeatedly rounded to whole tokens. Stopping hides further output while the bounded provider stream finishes to obtain actual billing. Closing your browser does not cancel a submitted request.
Owner testing with GPT Image 2.5 Flare or Sunburst uses an estimated provider reservation. The provider does not expose an output-token cap for these image requests, so actual provider USD costs can exceed the estimate or configured application budget. The authorised app-credit cap remains strict. Unexpected usage is held for review rather than charged beyond approval.
Uncertain billing
If final provider usage is unknown, no charge is invented. The reservation remains visibly pending until an administrator reconciles a verified usage receipt or confirms zero billing. Contact support if a request remains pending. Retrying is a new chargeable request with a fresh estimate.
Proposed refunds and reversals
Before live payments, the owner must approve a refund procedure consistent with South African consumer law, including applicable statutory rights. Proposed approach: review unused purchased-credit refund requests individually; test and promotional credits have no cash redemption promise. These drafts do not waive statutory rights or claim legal approval.
Verified refunds and reversals create offsetting ledger entries without removing original purchases. If refunded credits have already been used, the balance may carry debt and spending can be frozen pending reconciliation. Verified payment reversals use the original purchase amounts. Bob Pay sandbox payments cannot be refunded through its public refund API; reversal tests use synthetic receipts. Unverified partial reversal amounts freeze spending for administrator reconciliation. Existing Yoco refund notifications remain supported. Only the owner can start a real payment during this pilot. Chatify does not initiate cash refunds; those are handled externally by the owner and then recorded from verified evidence. Owner-enabled provider testing incurs real provider costs.
Owner review required
Approve retail prices, conversion rates, VAT, operating margin, consumer terms, the responsible legal entity, support and complaints contact, refund handling, privacy and financial retention before public retail activation. Contact [email protected] after the mailbox is verified by the owner.