FR Integration

Ryanair-specific booking flow with order confirmation, price transparency, and child seating rules.

Use this page when you integrate Ryanair booking flows.

When to use this flow

Use the FR flow when:

  • the airline is FR

  • order confirmation is required before final payment

  • you need popup or iframe confirmation

  • Ryanair-specific display and child seating rules apply

How FR differs from the standard flow

Compared with the normal booking flow, FR adds extra requirements:

  • price transparency for fare and ancillary charges

  • explicit passenger consent on the FR confirmation page

  • a mandatory orderCommit.do step before payment

  • special handling for child seating scenarios

  • FR-specific UAT and IP allowlisting

Standard FR booking flow

1

Call Search and keep the selected routingIdentifier.

2

Verify

Call Verify and keep the returned sessionId.

3

Create the order

Call Create Order with passenger, contact, and required FR fields.

At this stage, the OTA collects payment from the user. Do not call pay.do yet.

4

Confirm the order

Call Confirm Order. Use popup mode or iframe mode to display the FR confirmation page to the user.

5

Pay and issue

Only after the user completes confirmation, call Payment & Ticketing.

6

Poll final status

Use Query Order until orderStatus=2 and ticketStatus=0.

Confirm Order modes

Send the order number and a redirectUri. Atlas returns confirmationUrl. Redirect the end user to that page.

After the user confirms, FR redirects the user back to your redirectUri.

Iframe mode

Send the order number with iframe=true. Atlas returns confirmationUrl. Display that page inside your iframe flow.

In iframe mode, redirectUri is ignored.

Payment timing rule

Do not call pay.do before order confirmation finishes.

If the user does not confirm within 30 minutes after order creation:

  • the order expires

  • Atlas will not issue tickets

  • the OTA should refund the end user if payment was already collected

Required FR business rules

Price transparency

Display airline fare separately from:

  • airline payment fees

  • Atlas service fees

  • subscriber markup

  • ancillary charges

Read payment-fee data from cardChargeList in search and verify responses.

The FR confirmation page must collect user consent for:

  • terms of service

  • privacy policy

  • cookie policy

  • myRyanair account acknowledgement

Contact details

Pass both:

  • the passenger email

  • the subscriber email and company name in clientContact

This helps ensure both sides receive airline communication.

Child seating rule

FR applies special rules when children under 12 are included.

Important behavior

  • up to 4 children per adult

  • at least one adult may need a paid seat

  • children must sit in the same row as the accompanying adult

  • seat selection may become mandatory before payment

Atlas simplification option

If you are not ready to support full seat selection logic for FR with children:

  1. disable seat selection

  2. charge the mandatory seating fee

  3. let Atlas auto-allocate seats for the first adult and the children

Use childMandatorySeatingFee from search and verify responses.

Also ensure that one booking never contains more than 4 children.

circle-exclamation

UI guidance

Recommended maximum width:

  • popup: 1028px

  • iframe: 1028px

Suggested desktop/mobile breakpoint:

  • 768px

UAT requirements

IP allowlisting

Provide a static IP address for Ryanair allowlisting before live FR booking tests.

FR sandbox VCC test cards

Card number
Type

5200000000002235

Mastercard, approved

4000000000002701

Visa, approved

5476850000000002

Declined card

5100000014101198

Declined card

Use declined cards to validate payment-failure handling.

triangle-exclamation

FR test routes

  • DUB-KIR

  • KIR-DUB

  • DUB-LON

  • LON-DUB

  • MAN-DUB

  • DUB-MAN

UAT scenarios

Use the FR-specific UAT file below.

Last updated

Was this helpful?