The loop · step 01

ATOL certificates

A protected certificate, issued the moment a booking is paid.

Issue all three certificate types (Single Contract, Multi Contract and Flight Only) in moments, by interface or by API. Each is laid out in the CAA's ORS3 format, validated so no regulated field is ever truncated, and delivered to the consumer by email or downloaded for your own records.

Arrange a demonstration All capabilities

  • 3 types

    Single, Multi & Flight Only

  • ORS3

    CAA-format certificates

  • Server-set

    Issue time, never backdated

The reconciliation loop

  1. 01 ATOL certificates
  2. 02 Live licence limits
  3. 03 Self-building returns
  4. 04 Lock-in & discrepancies

Stamped by the system, not the sender

Every certificate carries your organisation, your ATOL number, and an issue time set by the server, never supplied by the person issuing it. A certificate cannot be backdated, which is what makes it stand up to scrutiny. For packages, the matching Confirmation document is produced alongside, so the consumer receives the full protected record in one step.

New certificate

SingleMultiFlight Only

Lead passenger

J. Whitfield

Departure

02 Sep 2026

Protected cost

£4,820.00
Issue certificate

Issue time is set by the server. A certificate cannot be backdated.

Amend and cancel, with the history intact

Bookings change. Amend or cancel a certificate and the change is versioned: the before and after are both kept, with the reason recorded. Where an amendment falls inside the 72-hour window, the consumer is re-supplied automatically. Every version is held, so you can always show what was issued, and why it changed.

Certificate amended

v1 → v2
Passengers
34
Protected amount
£4,820.00£6,110.00

Reason: passenger added · within 72h · consumer re-supplied

Built in

What's included.

  • Single Contract, Multi Contract and Flight Only types
  • Passenger manifest with ages on every certificate
  • Confirmation document generated for packages
  • Delivery by email, or download as PDF
  • Amendments and cancellations, fully versioned
  • Reason captured on every reduction or cancellation

Questions

Straight answers.

Which certificate types are supported?

Single Contract, Multi Contract and Flight Only: the three ORS3 formats in use today. A Multi Contract itemises up to four booking lines (flight, accommodation, car hire, other), each with its own description, supplier reference and price.

Can a certificate be issued under the wrong ATOL number?

No. The organisation name and ATOL number printed on a certificate always come from your holder account, never from form input, so it cannot be issued under the wrong licence.

What happens when a booking changes after issue?

The certificate is versioned. The original as-issued passenger count and protected cost are kept untouched, the new values recorded alongside, with the reason and a full before/after history. A change more than 72 hours before travel re-supplies the consumer automatically; inside 72 hours it is recorded. Prior versions are always retained.

Is the certificate branded with our logo?

No. The CAA prescribes the format: a plain yellow document with no operator branding, on the certificate or its delivery email. Regulated fields are validated on input, so nothing is ever silently truncated.

Is APC shown on the certificate?

Never. The ATOL Protection Contribution is internal liability, tracked in your returns. It appears on neither the certificate nor the package Confirmation.

Certificates in the CAA's ORS3 format. Licence usage, returns and APC on the regulator's own basis.

The loop · step 01

See it on your own ATOL.

Issue Single Contract, Multi Contract and Flight Only certificates, each carrying your ATOL number and a server-set issue time that cannot be backdated.

Arrange a demonstration All capabilities