This page explains when and why charges appear. Amounts and tax are always on the invoice and in Stripe.

Billing cycle

New subscriptions are anchored to a monthly boundary (first day of the next calendar month, UTC, in the current server implementation). The Subscriptions view notes that recurring invoices align with monthly cycles. Your Invoices page lists actual issue and due dates.

Automatic collection

Subscriptions use Stripe charge automatically. The default payment method pays open invoices on success. If Stripe cannot charge, see Failed payments.

Plan and add-on changes

When you upgrade a plan or change add-on quantities, Stripe updates subscription items. The product often uses proration behaviours such as always_invoice so partial-period differences become immediate invoice lines or adjustments. The exact proration lines appear on the next relevant invoice.

Subscription schedules can stage future phases (for example next-cycle plan changes). When a schedule is active, upcoming items may display in the product before they bill.

Compute credits and line items

Compute credits reduce the cash portion of eligible Worker Node purchases. Implementation applies credits as invoice items that offset price data for the charge. See Compute credits.

Wallet balance

Wallet reflects Stripe customer balance (stored in cents internally, displayed as currency in the UI). Promotions, top-ups, or adjustments can change it. When an open invoice exists and the wallet balance covers amount due, the product may mark the invoice paid and decrement wallet as part of automated recovery (Failed payments).

Wallet is not the same ledger as compute credits, though both affect out-of-pocket cost.

Usage metadata

Stripe subscription metadata includes a type field for some products (for example distinguishing Worker Node style subscriptions). Behaviour for failed payments can depend on that type. Platform usage subscriptions follow the general retry and wallet rules in this section.

Upcoming invoice reminders

The platform can enqueue upcoming invoice reminder jobs so you receive notice before large renewals. Email and in-app messaging depend on configuration; keep contact info current under Profile → Account.

Plan and limit emails

dFlow emails you for an upgrade, a completed downgrade, a past-due invoice, a cancellation, and usage above your plan. A scheduled downgrade, and a subscription that becomes active again after you pay, show in the product. Open Plans from the email when you need to review or pay.

• Upgrade. The subject is dFlow: Upgraded to your new plan. It names the previous plan and the current plan, and says the new plan applies now.
• Scheduled downgrade. You keep the current plan until the date in the in-app notice Subscription change scheduled. When that date arrives, the email dFlow: Your scheduled plan change is now in effect names the plan you are on and the effective date.
• Past due. dFlow: Payment past due includes when the billing period ends. Pay the invoice to keep the workspace active. If it stays unpaid, the email says the workspace returns to the Platform plan, purchased dFlow worker nodes are cancelled, and applications and data on those nodes are deleted. Custom worker nodes stay.
• Canceled. dFlow: Your subscription was canceled after an unpaid invoice. The workspace is on the Platform plan. dFlow worker nodes from that subscription are removed, and applications and data on those nodes are deleted. Custom worker nodes remain. You can upgrade again from Plans.
• Usage above the plan. dFlow: Action required on plan limits gives the date extra team-member or custom worker node access stays available. After that date, dFlow: Plan access is now restricted says that extra access is restricted. Custom worker nodes and their data are not deleted. Upgrade to restore access.

When a paid invoice makes the subscription active again, the product shows Subscription reactivated.

Related

• Plans and subscriptions
• Transactions and invoices
• Payment setup
• Billing issues