Third-party payments

Take a payment from someone other than the lead booker

Third-party payments allow someone other than the lead booker — such as a corporate finance team, parent, or sponsor - to pay for a booking.

The third-party payer does not need an Easol account. They simply open a secure payment link, enter their details, and complete the payment.

Note: Third-party payments must be enabled for your company by Easol. Contact support to request access.

How this differs from Group Pay

Third-party payments are not the same as Group Pay:

Third-party payer
- Not a guest on the booking
- Not added to the booking
- Does not need to log in
Group Pay
- Payers are guests on the booking
- Each guest pays their share

When to use this

Use third-party payments when:

A guest is travelling on a corporate budget and finance pays the invoice
A parent is paying for an adult child’s experience
A booker organises the trip but someone else settles the bill
You’re working a sales pipeline lead and want to send a direct payment link to the buyer

What’s supported

Initial payments (full or deposit) and balance payments
All payment methods:
- Stripe card
- Apple Pay / Google Pay
- TrueLayer instant bank transfer
- Braintree
- Stripe bank transfer
Refunds (processed as normal to the original payment method)
Multiple third-party payers on the same booking (e.g. one pays deposit, another pays balance)

What’s not supported

Payment plans (instalments are not available)
Easol account creation for third-party payers

Where to find and share a third-party payment link

You can generate and share a third-party payment link in four places:

1. From the booking balance section

Open a booking with an outstanding balance.

Locate the standard payment link
Copy the Third-party payment link shown below it

2. From a recommendation in the Sales Pipeline

Once a customer is assigned to a recommendation:

Go to the Share section
Copy:
- Recommendation link (for the customer)
- Third-party payment link (for the payer)

3. At checkout (admin-created bookings only)

If a booking is created on behalf of a customer:

At checkout, the customer sees “Who’s paying?”
- Pay myself → standard checkout
- Someone else is paying → generates a third-party payment link

Note: This does not appear on direct online checkouts.

4. From the “Balance due” email

The automated balance reminder email includes:

A pay-now button for the lead booker
A shareable third-party payment link

What the third-party payer sees

The payer completes a simple, no-login flow:

Contact details
Name, email, billing address
Payment choice (initial payments only)
Pay in full or pay deposit
Payment method
Card, wallet pay, bank transfer, etc.
Confirmation
A simplified confirmation page

Notifications

Payment confirmation email is sent to the payer
If payment is processing (e.g. bank transfer), a follow-up email confirms success or failure
Failed payments are only sent to the payer (not the lead booker)

If a balance remains:

The payer is added to reminder emails
They can use the same link to pay again

Refunds

Refunds work as normal:

Select Refund from the booking
Choose items and payer
Funds are returned to the original payment method

For bookings with multiple payers:

Each payer is listed separately
You can control how much each receives

Cancelled bookings and invalid links

If the link is no longer valid (e.g. booking cancelled or recommendation expired):

The payer sees a clear explanation page
No broken links or 404 errors

Documents and contracts

If your experience includes required documents (e.g. waivers or terms):

You can choose:

Block payment until signed (default)
- Payment is not possible until the lead booker signs
Allow payment without signature
- Payment can proceed
- Signature is still tracked separately

This setting can be adjusted per document.

Group Pay — when guests split the cost
Manually process a payment for a customer booking
Working with the Sales Pipeline
Intro to customer payment settings

Menu

Articles in this section