Authorize one automatic invoice payment at a reviewed time

The private invoice page can collect a saved payment method and, when activated, one authorization for one invoice balance at a specific time. The saved authorization belongs to that invoice and connected studio account. It is not a shared wallet or permission to charge future invoices.

Review the amount and payment window

In Payment authorization, choose Set up a payment method, then One scheduled automatic payment. Review the exact remaining principal, enter your name and email, and choose a payment time in the studio’s displayed timezone. The time must be at least one hour and at most one year away. Ambiguous or skipped daylight-saving times cannot be selected.

For example, a $1,200 remaining balance can be authorized for October 20 at 10:00 a.m. in America/Los_Angeles. The displayed consent authorizes one payment of $1,200 on that date or within the following 24 hours. It adds no gratuity. Read the complete authorization and select its consent checkbox before continuing to Stripe’s secure payment-method setup.

Completing setup does not mean the invoice has been paid. Return to the invoice to see the authorization and its payment-attempt status. The scheduler checks the invoice, balance, account, consent and payment window again before requesting a charge. A changed balance needs a new authorization; the system does not silently reduce, increase or move the approved payment.

This flow is limited to supported USD invoices using the studio’s connected payments. Mini-session deposits and remaining-balance invoices use their reservation payment flow and are excluded from automatic payment setup. An external payment link also remains with its own provider.

Save a method without authorizing a payment

Choose Save payment method only to complete secure setup without authorizing a charge. That choice creates no scheduled payment. A later automatic payment still requires a new, explicit amount-and-date authorization and its secure setup flow.

An active saved-method authorization must be cancelled before replacing it with a new authorization. The interface does not offer a global list of stored cards that another workspace or invoice can charge. Card or bank credentials stay with the payment provider; the invoice displays only a method label and the recorded authorization.

Cancel or resolve an interrupted attempt

Use Cancel authorization on the private invoice page to stop future payment requests under that authorization. Confirm the cancellation checkbox first. A payment already processing may still settle; cancellation does not hide its outcome or automatically refund it.

If payment-method setup is interrupted, use Continue setup / check status on the existing authorization. Keep the original request instead of creating replacements. Unknown charge outcomes retain the original attempt for reconciliation. An unresolved online or automatic attempt blocks another payment path until its outcome is known.

A decline or additional authentication requirement goes to review. There is no automatic decline retry. Cancel the authorization, allow its original attempt to reconcile or close, and use the invoice’s available payment option or contact the studio. If a payment is already settled, use the reviewed refund process described in invoice payments and disputes.

Read the record correctly

Active describes an authorization, not a successful payment. An attempt can be pending, requesting, processing, paid, cancelled, require action or remain uncertain. A settled principal receipt updates the invoice balance once even when callbacks repeat. Bank processing may take longer than the initial setup or request; provider-confirmed settlement is the evidence that matters.

A provider-verified successful payment creates one receipt email record. A declined or authentication-required payment creates one attention notice. Emails use the address saved in the authorization; these are transactional payment updates. Queued, sent, delivered, failed and uncertain email states are distinct. A sent result means the email provider accepted the request, while delivered requires its signed callback. An attention message that has not been attempted is cancelled if the payment no longer needs attention.

Workspace owners open Operations → Review automatic payments and receipt delivery to inspect the latest attempts and mail. Checking an uncertain payment retains its original request. Cancelling authorization does not reverse a settled charge. An unknown email outcome past the provider’s safe retry window requires provider review instead of blind resending. Bank receipts record when success was first verified, not the earlier authorization time.

The exact consent text remains visible with the authorization. A new invoice, a different studio account, a new amount or another payment date needs fresh consent. This single-invoice flow does not authorize an installment series or reuse permission across projects. A studio can separately prepare a finite installment payment plan with its own private link and explicit approval for each amount and date.

Coordinated launch activation

Development remains separate from live processing. The automatic-payment entry in the setup checklist covers connected-account credentials, signed setup/payment callbacks, scheduler recovery, isolated-account tests, cancellation races, bank verification, duplicate and out-of-order events, and ledger reconciliation. INVOICE_AUTOPAY_ENABLED stays disabled until that shared activation and sandbox rehearsal passes.

Local tests do not establish that a live card, bank debit, refund or consent flow has been verified with the provider. Existing financial records and settled outcomes remain reviewable while new automatic-payment requests are disabled.