Skip to main content

Stripe-hosted billing

Daspire uses Stripe-hosted pages for payment interactions. Organization owners can subscribe or buy row add-ons in Stripe Checkout and manage saved payment methods and invoices in Stripe Customer Portal. Daspire does not collect card or bank details.

Payment or entitlement status changes only after Daspire receives and processes a signed Stripe webhook. Returning from Checkout does not by itself confirm a payment. If Checkout is declined or abandoned, no add-on entitlement is granted.

Stripe supports one primary invoice email for the Daspire billing customer. The billing profile can also synchronize a supported customer Tax ID and a PO Number invoice field. Tax calculation can vary by account configuration and jurisdiction; adding a Tax ID does not guarantee a tax exemption.

Only the organization owner can create a hosted billing session. The Stripe customer is resolved by the Daspire server and cannot be selected by the browser.

Changing plans​

Daspire asks Stripe for an invoice preview before an existing subscription is changed. The confirmation shows the new-plan charge, the unused-current-plan credit, the final amount due today, and the next renewal amount and date. The same quote timestamp is used when the owner confirms the change.

Upgrades and downgrades take effect immediately. Changing between monthly and yearly billing starts a new billing period immediately; changing plans within the same interval keeps the existing renewal date. If a downgrade produces more credit than charge, nothing is charged today and Stripe keeps the remaining credit for a future invoice. A downgrade is blocked when current-month row usage is greater than the target plan allowance plus active row packs.

Row packs​

One purchased row-pack unit adds one million rows for the current UTC calendar month. Row packs are separate from the base subscription: changing plans does not refund or remove an active pack, and the pack expires at its original month end even when the base plan is billed yearly. Successful payment and entitlement are recorded from the signed Stripe webhook.

Prepaid Row Auto Reload​

The organization owner can opt in to Auto Reload from Billing and choose a usage threshold, the number of one-million-row packs per reload, and a maximum automatic spend for each UTC month. Daspire uses the default card managed in Stripe Customer Portal. The row pack is granted only after Stripe confirms payment; a decline or required card authentication adds no rows and the same invoice is retried after the owner updates the card. Auto Reload never creates a postpaid usage invoice.

Syncing stops at the current paid row allowance when no successful reload is available or the monthly cap has been reached. A later successful manual purchase or Auto Reload reactivates connections that Daspire paused for the paid limit.

Failed renewals​

A failed renewal pauses new syncs immediately. The following three days are a payment-recovery window, not free service time. The owner updates the payment method in Stripe Customer Portal; after Stripe confirms the renewal payment, Daspire restores the active plan and reactivates connections paused by the billing system.