Prepaid Credits, clearer billing visibility, and more control over production accessA team preparing to launch an identity verification flow needs a clear view of the service behind it. The developers need to know whether production access is active. The operations team needs to understand the available balance. The person responsible for spending needs to see what was purchased and how that balance has been used.When those answers are scattered across separate conversations and records, routine account management takes more effort than it should.With zkMe version 3.0, we are preparing an updated service experience that brings these questions together in the Dashboard. The upcoming payment changes introduce a prepaid Credits model, a distinct Production API Access purchase, and clearer records of purchases and service charges.For customers and chain ecosystems building with zkMe, the aim is practical: make the commercial side of running identity services easier to understand and manage alongside the technical integration.
A clearer view of your account
The updated Billing experience is designed around the information teams need to make everyday decisions: Available Credits, Production API Access status, purchase records, and Credits Activity.These serve different purposes. Available Credits show the balance available for eligible charges. Production API Access shows the account's access period. Purchase History follows Credits orders, while Credits Activity explains changes to the balance.Bringing them together gives customers a more useful picture than a balance alone. A funded account and an active access period answer different questions, and both matter when preparing production services.Consider a team expecting a rise in verification activity. It can review its balance, check the access period, and examine recent charges before deciding whether to purchase more Credits. That creates a clearer basis for planning and for discussions between product, engineering, and operations.
Prepaid Credits for service spending
Under the new model, customers purchase Credits using USDC. Credits represent prepaid service value within zkMe and are used for Production API Access and eligible service charges under the applicable billing rules.Customers follow the payment instructions shown in the Dashboard. Once payment is confirmed and the purchase is processed, the corresponding Credits become available in the account. Confirmation can take additional processing time, so a completed wallet transfer should be followed by checking the credited balance.This makes the account balance a useful operational reference. Teams can see the service value available to them and review how it changes as they purchase access or use supported services.The current Pricing & Billing Rules explain the applicable charges. Customers should review those rules together with the relevant terms when planning a purchase, since different services can have different billing units and conditions.Credits belong to the Dashboard account that purchases them. Teams operating multiple accounts should plan funding for each account, rather than assume that a balance can be shared across them.
Production access as an explicit account decision
Production API Access is a separate purchase paid from the Credits balance. Its fee covers a selected access period for production services enabled on the same Dashboard account. Service usage remains subject to its own applicable charges.The distinction is worth making explicit: buying Credits adds to the balance; activating Production API Access establishes the access period. Creating an API Key does neither of those things automatically.For a team completing setup, the sequence is straightforward. Review the applicable terms and pricing, purchase sufficient Credits, wait for the balance to be confirmed, then review and complete the Production API Access purchase. Check the account's access status before relying on it for production activity.Ongoing operation requires attention to both the access period and the balance needed for service charges. Customers should review the expiry date and the renewal settings available for their account. Where further action is required, completing it ahead of expiry helps teams plan for continued service use.This separation makes it easier to understand what each purchase does. Technical configuration, prepaid value, and production access become visible parts of the same account journey.
Records that make charges easier to understand
The updated experience also gives customers two complementary ways to review activity.Purchase History follows the purchase of Credits, including the order status and confirmed amounts. It helps distinguish a payment awaiting confirmation from a purchase whose Credits have already been added.Credits Activity follows the balance itself. It records Credits purchases, Production API Access purchases and renewals, and applicable service charges. Customers can review the change associated with an activity and the resulting balance.For verification activity, the available detail can show the billed Credentials and their contribution to the total. Where relevant, On-chain Mint records can include network and transaction information. This makes it easier to connect a balance change to the service activity behind it.A verification charge follows the applicable billing trigger; it should not be assumed to depend on a successful identity verification result. Customers should review the rules for the services they enable when estimating usage costs.That visibility gives teams a concrete starting point for reviewing spending, investigating an unfamiliar charge, or deciding how much prepaid value to maintain. It also makes conversations with zkMe support more focused because both sides can refer to the relevant account activity.
Preparing for the transition
We are contacting existing customers and chain ecosystems about the upcoming payment changes. Existing customers should follow the transition instructions provided for their accounts and review the applicable terms, pricing, and timing with their zkMe contact.As the updated experience becomes available to your account, start by checking the Dashboard you use for your integration. Review the balance, Production API Access status, and any account notices. Confirm who on your team will manage funding and access so those responsibilities are clear before the transition applies.Then review the expected service activity and the relevant billing rules. Ensure that funding covers the access purchase as well as anticipated service charges, and allow time for payment confirmation. After completing the required steps, check the recorded balance and access status in the Dashboard.If anything differs from your expectations, contact the zkMe team through your existing support channel or at contact@zk.me. Account-specific questions are best resolved against the instructions and records for that account.The purpose of this update is to make the responsibilities around running identity services clearer. Customers should be able to understand the payment model, see their account state, and know which action is needed next.
A stronger foundation for everyday service management
Privacy-preserving identity infrastructure needs a practical service experience around it. As an integration moves into regular use, funding, access, and billing records become part of the team's day-to-day work.zkMe 3.0 is designed to bring those elements closer together: prepaid Credits for eligible charges, visible production access, and records that help explain how service value is used.For customers, that means a clearer way to manage the relationship between their account, their spending, and the identity services their products depend on.Visit the zkMe Dashboard to review the information available for your account, and follow the transition guidance shared by the zkMe team as the update reaches you.