One Skavio company wallet for web tools and the API
Skavio File Toolbox, Transcribe, Meeting, Flow and the Processing API draw from one shared company credit balance. Teams can use that balance whether work starts in a browser or a server-side integration. The important distinction: the wallet stays the same, but each operation has its own charging unit.
The browser and API use the same balance
A document processed in Skavio Flow and a recording submitted through the Processing API do not need separate product credit balances. Both use the company’s Pricing V2 wallet, alongside File Toolbox conversions, Transcribe jobs and Meeting reports. The API is another way to submit supported processing work—not a separate credit system. Teams can choose the browser for hands-on work and the API for application-driven submissions without dividing their processing credits between those channels.
Shared credits do not mean a flat rate
The operation determines how credits are calculated. A page of document extraction, a minute of transcription and a file conversion are different units of work. API jobs use the corresponding operation’s rate.
- File Toolbox file work uses the larger of the number of started 25 MB units or started 10-PDF-page units, calculated per source.
- File Toolbox media processing is calculated per started minute, with a minimum charge.
- Transcribe is calculated per started minute, with a minimum charge per job.
- Meeting is calculated per started minute, with a minimum charge per job.
- Flow extraction is calculated per page, with a minimum charge per document.
A mixed workload, one company wallet
Consider a hypothetical team workflow: convert a PDF in File Toolbox, transcribe an interview in Transcribe, create a Meeting report from a separate recording, and submit an invoice to Flow through the Processing API. Those are four separate jobs with different charging units, but they all use the same company wallet. This is an illustrative workflow, not a customer result or a bundled offer. For duration-based work, a started minute counts even when it is only partly used. A 61-second recording therefore covers two started minutes. Transcribe and Meeting still apply their own rates; sharing the wallet does not make their charges identical.
From quote to reservation to charge
Check the measured quote before submitting a job. Submission reserves that quote from the company wallet. A successful job charges it once; a permanent failure releases the reservation. A reservation is not a completed charge, and releasing reserved processing credits is not the same as refunding a card payment. For integrations, keep these records distinct: reservations relate to submitted work, while completed charges represent credit consumption. Neither is a cash receipt or a measure of the underlying provider costs.
The trial allowance belongs to the company, too
Company signup receives 1,000 trial credits, subject to the current signup policy. That is one company allowance—not a separate trial balance for every product. Under the verified credit policy, prepaid credits do not expire and monthly credits roll over. These credit rules do not change the charging unit of an individual operation. A shared wallet also does not imply unlimited processing or establish individual spending caps, department budgets or transfers between companies.
Explore the workflows before planning an integration
Use the product workflow and its outputs to decide where a job belongs, then check its quote before submission. The common wallet connects the processing tools; it does not make their outputs interchangeable. Explore [Skavio Flow](https://www.skavio.eu/flow/) for document extraction into reviewed XLSX, CSV and JSON, and read the [Processing API documentation](https://www.skavio.eu/api/docs/) for supported server-side processing. Card checkout and credit top-ups are currently unavailable. These links are informational, not an invitation to immediate purchase.