Online payments and monthly billing: what to set up first.

Choose the simplest payment flow that fits

A hosted payment link may be enough for a standard service fee. A booking provider may already support deposits. A recurring service needs a subscription or equivalent billing arrangement that records authorization and future billing behavior. Choose the workflow first; do not add a separate checkout just because it is possible.

For example, a monthly bookkeeping service may need a setup invoice followed by recurring billing only after onboarding. A studio may need class purchases through its existing scheduler. A car shop may need an estimate approval before a deposit is requested. The website should describe the real sequence instead of asking every customer to pay immediately.

Keep the account and money with the business

Open the payment account under the correct business, with recovery and billing details the owner controls. Complete the provider’s identity and bank verification directly. Use the provider’s secure collection screens rather than asking customers to email card numbers or entering sensitive payment details in a general inquiry form.

Give an agency the access needed for the agreed connection and testing, not unrestricted responsibility for banking. Decide who issues refunds, reviews disputes, answers receipt questions, and reconciles payouts. Payment integration support does not automatically include daily financial operations.

Compare the full fee structure

Processing fees can differ for cards and bank debits, and subscriptions or standalone invoices can add separate product fees. At the time of review, Stripe lists US domestic online cards at 2.9% plus 30 cents and ACH Direct Debit at 0.8% capped at $5. Its pay-as-you-go Billing fee is 0.7% of Billing volume, separate from payment processing.

Use those published rates as an example, not a promise about your account. Check international cards, verification, disputes, refunds, currency conversion, and any optional products relevant to your business. The ACH processing cap does not cap a separate Billing fee. Ask for an estimate using your expected ticket size and actual payment methods, then confirm current terms with the provider.

References: Stripe [1]

Make recurring authorization and timing explicit

A recurring invoice sent by email is not necessarily an automatic debit. The customer must understand the amount or calculation, frequency, start date, and cancellation arrangement. Stripe’s subscription documentation distinguishes payment collection and subscription status; its ACH documentation describes the mandate collected through supported hosted payment flows.

If a service starts at website launch, do not silently start charging monthly care when a setup payment is made weeks earlier. Record the agreed activation event and any onboarding payment separately. Have a process for delays, upgrades, cancellation, and authorization changes. These are business decisions to agree with the customer before automating them.

References: Stripe Documentation [2]Stripe Documentation [3]

Test asynchronous and failed payments

A successful screen is not always the same as settled money. Bank payments can remain processing and can fail later. Build the process around the provider’s actual payment status rather than treating every checkout completion as final payment. Stripe documents the ACH payment lifecycle and the relevant verification and authorization steps.

Test the approved happy path, a failed payment, an interrupted checkout, a canceled subscription, and the customer’s ability to update details. If custom code reacts to payment events, assign responsibility for duplicate events, retries, and reconciliation. Do not build a custom billing system solely to avoid a modest software fee without budgeting its ongoing maintenance.

References: Stripe Documentation [3]

Put clear customer support around the transaction

Use recognizable business names on checkout, invoices, receipts, and statements where the provider supports them. Explain what the payment buys and how the customer contacts you. Make the refund or cancellation policy easy to find before payment; have suitable advice on legal and tax questions for your actual offer.

Review the first few real transactions carefully, then establish a routine for failed-payment notices and payout checks. BayBold can configure standard payment connections and agreed tools support. The business keeps control of funds, approvals, taxes, refunds, and disputes, while custom applications receive a separate maintenance scope.