Wallet balance
Best for first tests, SDK verification, and intermittent personal use. Users top up in USD and spend against actual usage.
Docs / Billing And Limits
Clear billing is part of the product.
OpenMagic should feel predictable: users can start with wallet balance, upgrade to monthly quota, understand fair-use limits, and see every payment and usage record in the console.
Billing modes
The site should sell a simple ladder instead of making beginners calculate raw token math.
Monthly quota
Best for repeat users and coding-agent workflows. The plan gives predictable quota, rate guardrails, and easier purchasing decisions.
Team / Enterprise
Best for higher volume, procurement, team support, custom limits, and provider-routing requirements.
What users can see
Every money and quota movement should be visible from the console.
- Orders: created, pending, paid, failed, refunded when supported.
- Payments: gateway, transaction ID, amount, currency, callback status.
- Quota: current balance, plan quota, daily limits, and usage records.
- API keys: per-tool key naming, status, remaining quota, and last access.
- Referral rewards: visits, signups, reward state, and payout notes.
Operational rules
These rules protect margin and support quality.
- All public prices and gateway amounts use USD.
- Expensive models can carry higher multipliers or plan restrictions.
- Monthly quota is not unlimited; fair-use and abuse controls must remain visible.
- Refunds and payment disputes should be handled from payment records, not chat memory.
- Enterprise customers should move to a sales-assisted path before they create operational risk.
When a payment succeeds
The callback should leave a complete audit trail.
Create order
The console creates an order with plan, amount, currency, user, and selected gateway.
Complete payment
Yuansfer or Stripe returns through the configured callback and signs the event.
Settle quota
The business layer marks the order paid, records payment detail, and grants balance or plan quota.
Send receipt
Email template and support context confirm the purchase for the user and operations team.
Warning: session_name(): Cannot change session name when headers already sent in /www/wwwroot/api.openmagic.ai/lib/UserSession.php on line 13
Warning: session_start(): Cannot start session when headers already sent in /www/wwwroot/api.openmagic.ai/lib/UserSession.php on line 14