For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Frontend Components
    • Overview
    • Quickstart
    • Core
    • Release notes
LoginSandbox
On this page
  • What’s in the SDK
  • How it works
  • Action requests
Frontend Components

Overview

Was this page helpful?

Quickstart

Next
Built with

The Solvimon Frontend SDK lets you embed billing UI elements directly into your product: invoices, subscriptions, checkout, and payment methods, without building any of it yourself.

What’s in the SDK

The SDK exposes two types of UI:

Screens are full-page compositions. Drop one in when you want a complete billing experience with minimal setup.

ScreenWhat it renders
customer-overviewA customer’s active subscriptions and payment methods
checkoutA full checkout flow for initiating a subscription

Components are single-responsibility widgets. Use them when you need more control over layout or want to compose your own billing page.

ComponentWhat it renders
invoices-listPaginated list of invoices with pay and view actions
invoiceA single invoice with line items, billing info, and payment attempts
invoice-detailsInvoice details by ID
subscriptions-listA customer’s subscriptions with cancel, renew, and view actions
billing-informationCustomer billing address and details
customer-payment-methodsSaved payment methods with add and manage actions
customer-wallet-balancesCustomer wallet and credit balances
payment-historyPayment attempts for a specific invoice

How it works

Every screen and component requires a portalObject: a short-lived token your backend generates via the Solvimon API. The SDK uses it to authenticate requests on behalf of the customer. Your frontend never handles API keys directly.

The typical flow:

  1. Customer loads a page in your product.
  2. Your backend calls the Solvimon API to create a portal URL for that customer.
  3. Your frontend passes the portal URL to the SDK when mounting the screen or component.

Action requests

Instead of navigating internally, the SDK fires action-request custom DOM events that bubble up to your app. You decide what happens when a customer clicks “Pay invoice” or “Cancel subscription”; the SDK just tells you it happened.

Actions include: view-invoice, pay-invoice, view-subscription-details, cancel-subscription, renew-subscription, edit-billing-information, add-payment-method, and more.