Manage course payments and AI credit adjustments

Platform owners and admins can use Payments to reconcile course orders and AI
usage. The page is restricted to roles that can manage accounts because it also
creates credit adjustments.

Review operations

Open Platform Admin → Payments to review:

• recent personal course, Business seat, and personal top-up orders;

• completed and pending totals;

• failed Stripe webhook events;

• open AI-credit reservations; and

• recent payment-event identifiers for provider reconciliation.

Configure the global AI credit rates

The Global AI credit settings section is the operational source of truth for new
AI requests. It controls:

• the token-to-credit exchange rate;

• the monthly instructor workspace allowance, used by previews and the workspace
  assistant;

• web-search and deep-research credit surcharges;

• the maximum size and cleanup timeout of a request reservation; and

• provider-cost estimates used in the Platform Admin report.

Enter a reason before saving. Each change receives a new rate version and is written
to the Platform audit log. Edge functions refresh these settings within about one
minute. Environment values remain fail-safe defaults if the settings table is
temporarily unavailable.

The save is protected against another administrator changing the rates while your
form is open. If the active version changed, refresh the page, compare the latest
values, and submit the change again rather than overwriting the newer decision.

The number of credits bundled with a paid course is not global. Configure that value
inside the course workspace under Settings → Commerce. Each Business assignment
still receives its own allowance; it does not draw from a shared organization pot.

Use Stripe Dashboard for payment-method, receipt, dispute, and refund operations.
Never grant purchased access from a pending Checkout Session.

Create a credit adjustment

1. Find the account under Platform Admin → Accounts. Select Adjust credits
   to open Payments with its immutable user ID selected, or use Copy ID when
   recording the support case elsewhere.

2. Choose Personal shared or Instructor workspace.

3. Enter a positive whole-number amount and a specific reason.

4. Select Create adjustment.

The adjustment creates a new immutable grant and a Platform audit event. It does not
rewrite prior usage. Negative adjustments and course-specific support grants are not
enabled in this first release. Learners buy shared top-ups themselves from Profile
→ AI credits; use an adjustment only for a documented correction or support case.

If the response is interrupted after you select Create adjustment, keep the same
values and try again. The page reuses the pending request identifier so an uncertain
response cannot create a second grant. Changing the user, amount, scope, or reason
starts a new adjustment request.

The grant or rate change and its Platform audit event are one transaction: neither is
kept when the other cannot be recorded. If a response is interrupted, retry the same
unchanged request from the page. The retained request identifier confirms the existing
result without duplicating it; reusing that identifier with different values is
rejected.

Reconcile unusual activity

Compare the payment order, webhook event, access record, grant, and usage reservation.
Escalate a completed payment with no matching access, a failed webhook, or a
reservation that remains open beyond the configured cleanup window.

Read Review course payments and refunds
for Stripe-specific steps.