Here are some of the most awaited product updates! From pricing rule logs that help maintain an audit trail to a customer portal designed for billing transparency. Read on to learn more about these updates and what’s coming next in this newsletter.
1. Customer Portal
Usually, to create and view a customer portal, the business needs to create a web app where their users can log in to view detailed information about their price plans, schedules, wallet details and history, and credit details and history.
That’s why at Togai we created the customer portal. In Togai’s customer portal, the customer can offer a solution for customers to provide their users with access to their price plans, schedules, wallet details and history, and credit details and history through a configurable customer portal.
2. Widgets
At Togai, we’ve created widgets to streamline the process which helps reduce the timeline by 4 weeks. Customers can simply choose the desired widget and provide the appropriate token.
Currently, Togai supports widgets for:
- Cost Metrics: Displays the cost incurred by an account(s) from usage over a specified time range.
- Credit Balance and History: Shows credits granted, available balance, running balance, and credit transaction logs.
- Usage Metrics: Shows the usage metric for a user for a chosen timeframe and usage meters.
How It Will Be Used
Users need to install the togai-ui-widgets package from the npm registry. After installation, they should initialize togai-ui-widgets with the token obtained from Togai via their user's session.
3. Auditability
1. Event Pipeline
Event Pipeline logs give users a clear understanding of the processing status of each event. Users can know if an event got processed, whether revenue was computed, and if the event was considered for the invoice. This feature helps users debug issues, such as missed events and ensures transparency in event processing.
How It Works
Event Pipeline provides detailed information about each event, the details available include:
- Event Schema: Shows the structure and data of the event.
- Matched Usage Meters: Indicates which usage meters matched the event.
- Account and Customer Details: Provides information related to the account and customer associated with the event.
- Price Plan Attachment: Confirms if the account had a price plan attached during the event ingestion.
By accessing these details, users can easily identify if an event was processed correctly if revenue was computed, and if it was included in the invoice. This comprehensive information helps in diagnosing and resolving any issues that may arise in the event processing workflow.
2. Workflow Logs
Marketplace Workflow Logs improve the reliability of our workflows. By implementing a retry mechanism and using idempotency keys, Togai ensures that workflows can recover from failures without causing data inconsistencies or duplicate actions.
This enhances the overall user experience and reduces the need for manual intervention in case of errors.
How Marketplace Workflow Logs Work
Marketplace Workflow Logs store detailed information for each workflow run, referred to as a "RUN." Each action within a run is logged, including the action performed, its status, and any relevant data or errors encountered.
Logs are grouped by RUN, allowing easy tracking of progress and outcomes for specific workflow runs.
When a workflow fails, the stored logs enable the retry mechanism to determine the exact point of failure. The retry logic uses this information to skip actions that were already successful and start from the failure point. An idempotency key, linked to the request payload that triggered the workflow, manages the actions during a retry.
This key ensures that actions marked as successful in the logs are not repeated, maintaining consistency and preventing issues like double charges or redundant updates.
For example, if a marketplace workflow fails at the "confirm payment intent" step, the workflow will be retried starting from that step rather than from the beginning. The idempotency key ensures that previous actions, like getting the Stripe customer ID and creating the payment intent, are not repeated. This makes the workflow more efficient and reduces the risk of errors.
3. Pricing Rule Logs
With Pricing Rule logs customers can ensure accurate and transparent application of pricing rules, facilitating better invoice management and compliance. Rule logs help with audits and also trace a particular event. Not just that, with rule logs you can see the values of the variables used and the computation results.
Here’s how it works:
When an invoice is generated, each pricing rule is processed in the specified order. The condition for each rule is evaluated using JSON logic. If the condition is true, the computation defined by the rule is executed.
The result of this computation is then applied to the relevant line item on the invoice, based on the action specified in the rule. This automated process ensures that all pricing adjustments are consistently applied according to predefined rules.
Pricing rule logs serve multiple purposes:
- Audit Trail: Provides an audit of how the pricing rules have affected the invoice.
- Verification: Customers can verify if the rule evaluation was a success or failure, determine the result, and understand how it impacted the invoice.
These are some of our enhancements! If you want to see what’s brewing with our product do take a look at our Changelog - we update it almost every week!
Watch how Togai solves your use cases!
- Within 5 minutes, you can configure Anthropic’s - (Claude) pricing model in Togai. See how we did it>>
- We solved billing for an Open Source Dev tools company. Take a look>>
We can't wait for you to dive in and start exploring these features. Want to get a peek at how these features work? Schedule a call with us, and we’ll take you through everything new and upcoming releases too!
Let’s speak over coffee about your billing needs!
Book your slot →
