> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/product-guides/extensions-and-integrations/special-integrations/fr-integration.md).

# FR Integration

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

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva in the Help Center for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this guide to plan and launch a Ryanair booking integration.

For endpoint-level implementation, use [FR Technical Integration](/api-document/product-guides/extensions-and-integrations/special-integrations/fr-integration/fr-technical-integration.md).

### Before you start

#### Who can integrate

FR integration is for registered B2C OTAs that sell directly to travellers.

You must have Atlas API integration capability. Meta display channels may be permitted only under their applicable conditions.

#### Approval and agreement

FR access requires approval in addition to your Atlas customer status.

1. Contact Atlas to confirm FR eligibility.
   * **Enterprise clients:** Contact your Sales or Growth Manager.
   * **Subscription Plan clients:** Email <info@atlaslovestravel.com>.
2. Sign the FR Content Addendum with Atlas.
3. Receive FR Subscriber approval and Atlas countersignature.
4. Receive the approved integration scope and access information.

Do not begin FR production sales until Atlas confirms the production arrangement.

#### Sandbox and locale

For sandbox access, provide the EU-based public egress IP of the testing team's office network. Do not provide an application-server or data-centre IP.

Choose the FR locale early. It controls the market and language used in the FR confirmation flow. See [Locale Reference](/api-document/support-and-reference/integration-reference/reference-data/locale.md).

### Build your booking flow

Your customer journey must clearly show:

* fare, ancillaries, and applicable charges as distinct amounts
* pre-purchase policy notices and active customer consent
* real contact email and phone details, plus required subscriber contact details
* the FR confirmation experience and a clear booking result
* guidance for managing the Ryanair booking after purchase

See [FR Technical Integration](/api-document/product-guides/extensions-and-integrations/special-integrations/fr-integration/fr-technical-integration.md) for the required behaviors and field-level implementation guidance.

#### Booking flow

The technical flow is Search, Verify, optional ancillaries, Create Order, Confirm Order, customer confirmation, Pay, and final order polling.

The complete FR sequence diagram includes the popup and iframe completion paths.

#### Confirmation and payment

Popup and iframe modes use different completion mechanisms. Design the confirmation experience so customers can complete it and return to a clear booking result.

Do not call `pay.do` before customer confirmation completes. The confirmation window expires 30 minutes after order creation.

#### Required business rules

Present fare and ancillary charges transparently. Explain relevant policies before purchase and collect active consent.

Collect real contact email and phone details, plus the required subscriber contact details. Use a supported `locale` value.

Child bookings can require specific seat handling. If your flow cannot meet it, block the affected child booking.

For sequence diagrams, completion modes, expiry, payment, ticketing, and field-level requirements, use [FR Technical Integration](/api-document/product-guides/extensions-and-integrations/special-integrations/fr-integration/fr-technical-integration.md).

### Validate and launch

#### Screenshot-based booking flow review

Before going live, submit screenshots of your end-to-end Ryanair booking flow to Atlas. Atlas reviews them against Ryanair's requirements.

Group screenshots by test scenario and label every stage clearly. Use test data or redact personal and payment information. Keep enough non-sensitive information visible to associate screenshots with the same test booking.

The screenshots must demonstrate:

* **Price transparency and consistency:** Show Ryanair's actual flight price separately from ancillary charges, payment fees, service fees, markup, and other package components. Prices, currencies, passenger counts, and selected services must remain consistent throughout the flow. Clearly explain any change.
* **Ancillary services, where offered:** Include paid baggage and seat selection and purchase. Clearly itemize their charges and show them in subsequent booking screens. Include both services in one test booking where possible.
* **Pre-purchase consent:** Show the Ryanair consent statement and acceptance checkbox before purchase, including the myRyanair account acknowledgement. Each named policy must link to its official Ryanair policy page.
* **Ryanair confirmation:** Show the confirmation page opening and the passenger completing confirmation through your popup or iframe flow. Then show the subsequent screen on your platform.
* **Payment and successful ticketing:** Show payment completion and the final successful ticketing result. Include a masked booking reference or airline PNR to associate evidence with the test booking. Payment success or a PNR alone does not demonstrate successful ticketing.

Cover every payment model in your approved integration scope. Passenger-details screenshots are not required only to repeat contact-data validation completed during API testing.

Provide disruption or involuntary-refund handling evidence separately, where applicable and available in the test environment. If a required scenario cannot run in the sandbox, describe the limitation. Atlas will confirm an alternative validation approach.

Submit the screenshot pack to your Atlas contact. Atlas will coordinate the review and production arrangements.

Screenshots validate the customer journey. Technical testing must also verify backend confirmation handling, callback or message validation, payment sequencing, and final order-state handling.

#### Illustrative examples

Use redacted, annotated examples to show price transparency, pre-payment consent, and the Ryanair confirmation experience. These examples help teams understand the expected journey. They do not replace their own booking-flow evidence.

**Price transparency**

<figure><img src="https://61296268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUcaRG2qIaBgtVwgrBEGX%2Fuploads%2FV1nbmTTxDSmDgddxxPTt%2Ffr-ancillary-price-transparency.png?alt=media&amp;token=df558008-c0cd-460c-9713-5d6729f94187" alt=""><figcaption></figcaption></figure>

**Consent before payment**

<figure><img src="https://61296268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUcaRG2qIaBgtVwgrBEGX%2Fuploads%2FSjxziFodsSauPpXZCpZD%2Ffr-passenger-consent.png?alt=media&amp;token=0f9f9dd3-df22-412f-899f-c5d7ea1f8dc4" alt=""><figcaption></figcaption></figure>

**Ryanair confirmation popup**

<figure><img src="https://61296268-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUcaRG2qIaBgtVwgrBEGX%2Fuploads%2FoDCrUwL8nJF5wgmZLmnb%2Ffr-confirmation-popup.png?alt=media&amp;token=2c75a97c-8df7-4ed9-a0aa-ce24e5b06d09" alt=""><figcaption></figcaption></figure>

#### Go live

Complete FR approval and booking-flow review before production. Then confirm the production content arrangement with Atlas.

Sandbox test access does not establish production access. Confirm the production credentials, addresses, and any production allowlisting separately with Atlas.

### After booking and support

Tell customers to sign in or create a myRyanair account to manage their booking after purchase. Do not add a pre-ticketing login or identity-verification step for this purpose.

For refund handling, see [Ryanair (FR) Refund Policy](/popular-topics/post-booking/refund/ryanair-fr-refund-policy.md).

### Further references

* [Locale Reference](/api-document/support-and-reference/integration-reference/reference-data/locale.md)
* [Confirm Order](/api-document/product-guides/booking/booking-step-guides/confirm-order.md)
* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
* [Production Go-Live](/api-document/readme-1/production-go-live.md)
* [Special Integrations](/api-document/product-guides/extensions-and-integrations/special-integrations.md)