Accept card payments through a configured Stripe account, including supported customer authentication challenges and saved-card renewal collection.

Use a configured Hyperswitch deployment to access its processor routing and checkout experience. The current integration requires customers to enter payment details for each payment rather than charging stored methods.

Accept Bitcoin and Lightning invoices through a configured BTCPay Server. Customers pay renewal invoices manually; the integration does not charge a stored crypto payment method.

Choose an active payment gateway for an operator and pin individual customers to a supported gateway, enabling a controlled payment-provider migration.

Let customers add, view and manage supported Stripe payment methods, with card-expiry information and renewal reminders.

Allow a customer to select an owned, compatible saved payment method for an eligible subscription, and show which method will be used for renewals.

Process authenticated provider webhooks and retrieve provider payment state for reconciliation, with supported polling or backfill paths for missed events.

Show safe plain-language explanations and available provider codes in staff payment history. Customer recovery guidance distinguishes outstanding, pending, already-paid and ended-service cases.

Show recorded attempts and actual scheduled retry or next-action evidence. Historical failures remain visible after payment succeeds; an invented retry time is never presented as scheduled work.

Track supported card refunds and BTCPay claimable pull-payment refunds. Pending provider outcomes remain distinct from completed refunds.

Issue invoices with configured numbering series and generate customer billing documents. Credit and debit notes have their own series, while imported history stays distinguishable from newly issued documents.

Record payments, allocations, credit notes, debit notes and refunds as separate financial events instead of editing away the original transaction history.

Show invoice balance information that accounts for recorded allocations, credits and debit notes. The server rechecks the balance when a payment or credit action is performed.

Compare recorded invoice lines and adjustments with prior billing to explain supported price, quantity, proration, tax, discount and credit changes. Missing or ambiguous history is identified.

Let customers choose a month and download a CSV statement of recorded billing activity with source references and separate currency totals. It is a statement of platform records rather than a bank statement.

Maintain prepaid account credit and apply eligible same-currency credit to purchases or outstanding invoices through the supported billing workflows.

Allow authorised staff to record bank transfers or cash payments and preserve their effect in the billing ledger.

Configure product tax treatment and store the tax information used for the order, so later settings changes do not silently rewrite that history.

Load EU standard VAT rates, refresh supported rates from the European Commission source and flag changes outside configured automatic bounds. Supported VIES checks and card-country comparisons aid review.

Use supported currencies and locked conversion rates for presentment charging while retaining the operator’s billing currency. ECB reference rates, conversion spread and business-day staleness rules support this workflow.

Support configured percentage or fixed late-fee rules with grace and minimum settings. These settings currently require the API or deployment administration rather than a console editor.

Issue renewal invoices ahead of the term, collect supported stored-card payments according to the configured schedule and send due-date or card-expiry reminders.

Use configured payment-recovery, suspension and termination windows, with an overdue review queue. Eligible suspended services can resume after settlement; paying historical debt does not automatically restore a terminated service.

Show the price and eligible proration for a plan change. Paid upgrades wait for settlement before the active plan changes, with service synchronisation handled separately.

Let eligible customers review a cheaper plan, see its effective date, schedule it and cancel the request before application. The current flow preserves paid access and does not automatically issue an unused-value downgrade credit.

Offer reviewed additions or removals from configured families of up to three compatible extras for supported account or tenant plans. Prices and entitlement changes follow the reviewed selection; additions can require payment.

Enable a pause allowance on eligible monthly services backed by supported, unshared Emby, Jellyfin or Bloem accounts. Customers review the restart date and billing impact; completed pauses preserve unused paid time.

Let eligible customers review and request a new monthly billing day, with the adjustment and outstanding billing or plan-change conditions checked before acceptance.

Display eligible upcoming renewals, export an iCalendar snapshot or create a revocable calendar subscription. Optional calendar reminders keep estimated, held and cancelled entries distinguishable.

Let customers request immediate or end-of-term cancellation for staff review. Approval or rejection is recorded and communicated; bundle-wide and individual service consequences remain explicit.

Add email-only accountant or billing contacts who explicitly accept the allowed billing notifications and copies. They can be removed and receive no customer-portal, support or service-management access.

Preview selected subscriptions and target plans with currency, tax, recurring-price differences and exceptions. Applying a reviewed selection rechecks the current records rather than relying on an old preview.

Connect paid service orders to account creation or invitation, suspension, resumption and termination through supported server adapters and background jobs.

Configure Bloem, Silo, Emby, Jellyfin, Plex, RomM and BookOrbit targets. Account creation, invitation and available customer controls depend on each adapter and server capability.

Install approved runtime plugins for extra delivery systems, including the separately supplied request and Emby management system adapter. A configured server type alone does not install or enable its integration.

Test configured servers, record their identity and load supported catalogue or library information for appropriate storefront presentation.

Place new services through weighted, least-filled, round-robin or explicit-pin pool rules. Keep supported account and guaranteed-transcode capacity constraints part of placement.

Map supported products to exact entitlement-template revisions covering relevant libraries, playback, profiles, streams, downloads, requests, quality and permissions.

Inspect recorded provisioning and entitlement-delivery work, including failures and pending dependencies. Payment or job acceptance alone is not presented as proof that remote access already works.

Preview expected and observed policy across selected supported accounts, review exclusions and execute a bounded operation with monitoring and supported retry or restore paths.

Offer available password, username, invitation or credential-handoff actions for the connected service. Newly issued one-time credentials stay behind the authenticated portal rather than being emailed.

Let customers manage supported profiles, registered devices and active sessions from their service page when the server advertises those capabilities.

Sell supported tenant services with account-slot and guaranteed-transcode reservations against the host’s configured capacity. Tenant quotas can change in place through eligible plan changes.

Give tenant customers controls for quota-bounded members, profiles, devices, sessions and supported one-time credential handoffs.

Keep accounts-in-use and purchased limits visible. Supported tenants can be frozen when a downgrade leaves them above their allowed quota until the limit is satisfied.

Publish managed-service products backed by application definitions and hosts that the operator supplies.

Create supported Docker deployments or Proxmox LXC instances using the configured definition, template and host credentials.

Let customers start, stop and restart their own supported applications and inspect the recorded deployment state.

Offer redeploy for supported Docker applications while retaining declared data volumes. Proxmox LXC redeploy is intentionally unsupported rather than discarding the machine’s state.

Keep application lifecycle actions and outcomes in the platform’s operational record, with controls appropriate to the chosen driver.

Use an installed accounting plugin, such as the separately supplied Moneybird connector, to export supported invoices, payments, credit notes and refunds.

Follow a billing record through its payment and export references, compare recorded booking amounts and currencies and inspect mismatches with source links.

Use authorised retry and reconciliation controls for eligible records, skipping already-synchronised documents and retaining uncertain outcomes for review.

Detect discrepancies between recorded accounting totals and billing records. Connector booking evidence is distinct from a live provider balance or a certification of the books.