Purchases, receipts, and refunds
Follow credit from a verified payment event into the project ledger.
The hosted console currently uses a billing preview. You can inspect the purchase flow, but it does not send a live payment or add spendable credit. A completed preview explicitly leaves the balance unchanged.
Live purchase flow
When live billing is enabled, open Billing, select Add credits, and choose an amount. The console offers $10, $25, $50, and $100 shortcuts, with a custom amount field. The current purchase form accepts whole-dollar amounts from $10 to $1,000.
Polar handles checkout and payment details. Applicable tax is shown at checkout. Internalize credits the project's paid net principal; tax is not converted into inference credit.
Keep the selected project in mind. Credits belong to the project associated with the checkout, not to every project in the account. The current console does not expose self-service balance transfers between projects.
Payment confirmation
Returning from checkout does not itself create a balance. A verified payment event updates the durable payment record and credit ledger. This prevents an unverified redirect or repeated page refresh from granting credit.
Duplicate events for the same paid order do not issue credit twice. If checkout succeeded but the balance has not updated, inspect the receipt and project, then allow the payment event to reconcile. Do not immediately buy again merely because the first browser redirect was interrupted.
Receipts and credit activity
The Billing workspace shows the most recent 100 ledger entries, including purchases, settled usage, and refunds. References link an entry to its payment order or job identity. The display can round dollars for readability, while the ledger retains micro-USD precision.
Receipts & payment details opens the payment portal when live billing is configured and the project has payment history. It is unavailable in the current preview. Payment-card details are managed by Polar rather than stored in the console's project record.
Refunds
A refund removes the credited principal associated with the refunded amount. It does not erase historical inference or learning usage. If the resulting balance no longer covers open reservations, the project can be frozen against new spending until the mismatch is resolved.
Refund handling is monotonic: a later duplicate paid event cannot undo a recorded refund and mint the credit again. Do not try to repair a mismatch by manually changing a displayed balance or repeatedly revisiting a checkout URL.
The console does not provide a self-service refund initiation control. Contact team@convergingthought.com with the authorized project and order reference for a billing question. Do not include card numbers, full payment credentials, API keys, or source content.
For a usage discrepancy, start from the job's settled charge and the corresponding ledger entry. See Credits and pricing and Usage to distinguish a reservation, a charge, and a rounded summary.