Skip to main content

What clients see when making a payment

A high-level overview of what your clients see when paying through Legl, including payment options and confirmations.

Michelle Rufer avatar
Written by Michelle Rufer
Updated this week

Overview

When you send a Pay Request or share a payment link, your client is taken to a secure, branded payment page. The experience is designed to be simple and similar to a standard online checkout, whether they are paying by card, Pay by Bank, or through a payment plan.

This article explains what your clients see and what happens during and after payment.


What this covers

  • Branded Pay Request links

  • Card payment experience

  • Pay by Bank experience (if enabled)

  • Payment Plans

  • Checkout links and website payments

  • Email receipts and confirmations

This article focuses on the client experience. It does not cover how to create or manage payments in the dashboard.


How this works at a high level

When you create a Pay Request, Legl generates a secure payment link. This can be sent via email (from [email protected]) or shared directly.

From the client’s perspective:

  1. They open the link.

  2. They review the payment details.

  3. They select a payment method.

  4. They complete the payment.

  5. They receive confirmation by email.

Once paid, the payment status updates automatically in your Payments dashboard.


What your clients see

1. A branded payment page

The payment link is branded with:

  • Your firm’s logo

  • Your firm’s contact details

  • The payment amount

  • Any invoice or matter reference

  • Any attached documents (such as invoices)

Before proceeding, the client must agree to the Terms of Use and Privacy Policy.


2. Payment method selection

Depending on your firm’s settings, clients may see:

  • Pay by Card

  • Payment Plan


3. Paying by card

If the client selects Pay by Card, they will:

  • Enter their card number

  • Enter expiry date and security code

  • Enter their billing address

  • Click Pay

The experience is similar to a standard online checkout.

Once completed, they immediately see confirmation on screen and receive an email receipt.


4. Payment Plans

If you create a Payment Plan, the client:

  • Enters their card details once

  • Agrees to the plan terms

  • Receives automated reminders before each instalment

  • Has instalments collected automatically on the scheduled dates

They do not need to re-enter their card details for each payment.


5. Checkout links and website payments

If you use a Checkout link or embed a payment button on your website, the client will:

  • Enter their name and email address

  • Enter any required invoice or matter reference

  • Enter the payment amount

  • Choose a payment method

  • Complete payment as above

This option is often used for “Pay my bill” pages or invoice footers.

Note: The Support team can configure the Invoice reference to follow a specific format, so that only real invoice references are accepted. Contact [email protected] to get this set-up.


What happens after payment

  • The client receives an email receipt confirming the payment.

  • The payment status updates in your Payments dashboard to Paid.

  • You can view full payment details, including billing address and card type used.

  • Funds are transferred to your firm via scheduled daily transfers.


When you would use this

You will typically send clients to this payment page:

  • When requesting payment for an invoice

  • When collecting onboarding fees

  • When taking money on account

  • When requesting search or court fees

  • As part of an Engage workflow with a payment step included


Important:

  • Pay Request emails are sent from [email protected].

  • It is not possible to directly CC a third party into the Pay Request email. If needed, you can share the payment link manually.

  • Card details entered by clients are not stored on the platform after payment.

  • Payment method availability (e.g. Pay by Bank, AMEX, international cards) depends on your firm’s settings.

Did this answer your question?