> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-page/details/help-a-client-make-an-online-payment.md).

# Help a client make an online payment

The client pays an unpaid scheduled amount from the **Payments** tab in the Client Portal. A payment schedule row states what is expected; it becomes a received payment only after FlowerBuddy records a successful provider transaction.

Before guiding the client, [configure the event's online payment methods](/reference/event-page/details/configure-payment-options.md), confirm that the [Client Portal is published](/reference/event-page/proposal/publish-and-client-portal.md), and review the schedule. Use [manage invoices, payments, and receipts](/reference/event-page/details/manage-invoices-payments-and-receipts.md) when you need to record a payment received outside the online flow or review the event's payment records.

## Open an eligible payment row

Ask the client to:

1. Open the Client Portal link.
2. Select **Payments**.
3. Find the unpaid scheduled row they want to pay.
4. Review the payment name, amount, and due date when due dates are shown.
5. Select **Pay**.

The **Pay** control appears for an unpaid row when web payments are available. FlowerBuddy can disable online payment when the event is not **Booked** or when the event has amendments. If the client cannot select **Pay**, check the event status, amendment state, and payment configuration before asking them to try again.

## Review the amount and method

The checkout opens with **Complete payment** and an **Amount Due** summary. The summary can separate the base payment from an application fee, an ACH discount, or an optional tip on a final payment.

When more than one method is available, the client selects **Card** or **ACH** under **How would you like to pay?**, reviews the method-specific total, and selects **Continue**. The connected payment processor then displays the fields needed for that method. The client should check the total and complete the provider checkout with their own payment and billing information.

## Submit the payment

The client selects the final **Pay** button, which includes the total amount. The provider processes the payment and FlowerBuddy waits for confirmation before treating the row as paid.

For a payment FlowerBuddy records as successful, the client's row updates to show the paid amount and paid date. In the florist's **Details > Payments** table, the paid row also identifies the payment method. FlowerBuddy sends a payment receipt to the email address supplied during checkout. That address does not have to be the event's primary client contact, so tell the client to use the address that should receive the receipt. The client returns to **Payments** to see any remaining unpaid rows.

ACH payments can require additional bank verification or processing time. If the checkout says the provider accepted the payment but FlowerBuddy has not confirmed it, the client should not submit the payment again. They should follow the provider's instructions, return to the payment link, and refresh **Payments** later.

If a client reports that money was submitted but the row is still not paid, check **Details > Payments** before asking them to try again. Use [manage invoices, payments, and receipts](/reference/event-page/details/manage-invoices-payments-and-receipts.md) to review the recorded payment, transaction details, or receipt options from the florist side.

## Payment fields that do not load

If **Pay** opens the checkout but the card or bank fields keep loading or never appear, treat that separately from a missing or disabled **Pay** button. The payment provider's fields may be blocked by a browser extension or network restriction even when the event settings are correct.

Before the client submits a payment, ask them to try another browser or device, temporarily allow the payment page in any content blocker, or try another network such as cellular data. Have them reopen the Client Portal and check whether the fields appear.

If the fields still do not load, contact FlowerBuddy support with the provider, browser, device, and visible message. A screenshot can show the loading state without containing payment details. Repeatedly changing the event settings or disconnecting the provider does not resolve a browser or network block.

If the client already selected the final **Pay** button or received a processing message, check the payment record before another attempt. The missing-fields checks are for a checkout that has not yet accepted payment information.