Credits & Billing

How Credits Work

Every AI processing call consumes credits from your organization's balance. Credits are deducted per file processed — not per batch or per request group. The exact cost per file depends on which AI model is configured in the template used for that document.

Key points:

• Credits belong to the organization and are shared across all projects within it
• Deductions happen automatically at the moment a file is processed
• If the balance is insufficient, processing is blocked before it starts
• Credit costs vary by AI model — lighter models cost fewer credits than premium ones

---

Credit Types

Ocriva supports two ways to add credits to your organization. They differ in expiry behaviour:

Type	Source	Expiry	Best For
Top-up	One-time purchase	Never expires	Pay-as-you-go usage
Package	Monthly subscription	30 days from purchase date	Regular, predictable workloads

---

Purchasing Credits

One-Time Top-Up

Top-up credits are a straightforward way to add a fixed amount of credits whenever you need them. They never expire and carry over indefinitely.

1. Go to Organization → Billing
2. Click Top Up Credits
3. Select the credit amount you want to purchase
4. Complete payment via Stripe
5. Credits are added to your balance immediately after payment is confirmed

Subscription Package

A subscription package adds a recurring credit allocation each billing period and also unlocks higher usage limits for storage, requests, webhooks, templates, and projects.

1. Go to Organization → Billing
2. Browse available plans and click Subscribe
3. Complete the checkout via Stripe
4. Credits are added to your balance immediately
5. On each renewal, a new allocation is added — unused package credits from the previous period expire

---

Checking Your Balance

You can view your current credit balance in several places:

• Dashboard — shows the current balance at a glance
• Organization → Billing — detailed view including credit history, transactions, and usage breakdown
• API — the organization details endpoint includes the current credit balance in the billing.credits field

---

How Credits Are Deducted

Credits are deducted atomically at the point of processing. The system checks whether the organization has a sufficient balance before starting, and then applies the deduction with optimistic concurrency to prevent race conditions in high-throughput scenarios.

The cost per document is determined by the AI model assigned to the template:

Model	Estimated Cost per Document
GPT-4o-mini	~1 credit
GPT-4o	~5 credits
Gemini Flash	~1 credit
Claude Haiku	~2 credits

(Actual costs are defined in the platform's MasterCreditModel configuration and may vary. The values above are illustrative.)

Deduction flow:

1. Upload request is received
2. System looks up the credit cost for the selected AI model
3. Balance check — if credits are insufficient, the request is rejected
4. Processing begins and the credit deduction is applied atomically
5. Credit history is updated with the deduction record

---

Usage Limits by Package

In addition to credits, each subscription package enforces the following usage limits for your organization:

Limit	What It Controls
maxCredits	Total credits included in the package per period
maxStorage	Maximum file storage in GB
maxRequestClassA	Maximum number of AI processing requests
maxWebhookEndpoint	Maximum number of webhook endpoints
maxTemplates	Maximum templates per project
maxProjects	Maximum projects per organization

Free-tier and lower-tier packages have smaller limits. Upgrading your plan increases all limits simultaneously.

---

Billing History

All financial transactions and credit movements are recorded and accessible from the Billing page:

• Payment records — every Stripe checkout session, including amount, date, and invoice link
• Credit additions — top-ups and package renewals with timestamps
• Credit deductions — per-file processing costs with model and file reference
• Invoice downloads — PDF invoices for accounting and expense reports

To view billing history:

1. Go to Organization → Billing
2. Scroll to the Transaction History or Credit History section
3. Use date filters to narrow the range

---

Stripe Payment Flow

Ocriva uses Stripe for all payment processing. No card data is stored on Ocriva servers.

Checkout flow:

1. Select a top-up amount or subscription plan in the Billing page
2. You are redirected to a Stripe-hosted checkout page
3. Enter payment details on the Stripe page
4. On successful payment, Stripe sends a checkout.session.completed webhook to Ocriva
5. Ocriva processes the webhook, adds credits, and updates your billing record
6. You are redirected back to the Billing page showing the updated balance

If a payment is interrupted or the browser is closed before completion, credits are not added. Return to the Billing page and start a new checkout session.

---

Best Practices

• Monitor credit balance regularly. Low credits will block processing without warning. Check the dashboard before scheduling large jobs.
• Use cost-effective models for routine documents. GPT-4o-mini and Gemini Flash deliver strong results at a fraction of the cost of premium models.
• Reserve premium models for complex or critical documents. Use GPT-4o or Claude for documents where extraction accuracy is business-critical.
• Top up before package expiry if you expect overflow usage. Top-up credits do not expire and can serve as a safety buffer.
• Review credit history monthly. Sudden spikes in deductions can indicate misconfigured templates or unexpected processing volume.
• Upgrade your plan if you are hitting usage limits. Hitting maxRequestClassA or maxStorage will block operations even if you have credits remaining.