SNCF Certification Supplier Requirements

SNCF requires certification and approval before granting both pre-production and production credentials to begin coding.

• This process begins by contacting your Account Manager, who will create an internal support request to begin the provisioning process.
• The Account Manager will also work with you to complete and submit the required SNCF provisioning form to request pre-production credentials.
• For PAO (3C) click here.

Prerequisites

One of the prerequisites is that the subscriber (the Universal API developer) must have a retail agreement with SNCF. Contact SNCF to begin the contract agreement process as soon as possible, so that SNCF can issue pre-production credentials.

Once the application is approved and pre-production credentials are issued, Travelport will add the credentials to your subscriber agreement and profile so that you can begin coding in the pre-production environment.

Testing

As you are building your application with SNCF content on the pre-production system, think about the certification checkout that SNCF requires before going live:

• The move-to-production process will begin with a joint SNCF-subscriber workshop.
• There are a number of use cases that SNCF will go over with you and require you to pass before going live. These will be provided to you with your pre-production credentials, so you have them early enough to keep them in mind while you’re building your workflow.

• SNCF will monitor the progress of your testing around these use-cases.

Note: The standard Universal API support certification process still applies, in addition to the required SNCF certification.

SNCF Loyalty Cards for Pre-Production Testing

Last Name	First Name	SNCF Loyalty Card
PETIT	DAMIEN	29090109000008564 VG
LEBOEUF	STEPHANE	29090109000009497 VP
SMITH	JOHN	29090109062518088 VP
ALEX	LOURS	29090109062518336 VP
CANETTA	ROMANO	29090109687508829 VO

Production

When you pass your use cases, SNCF will grant approval for production. SNCF also provides another set of production credentials that will be added to your subscriber agreement by your Account Manager. Travelport will then provision you for Universal API production access, and at this point you can “go live.”

Exchanges

Rail 41.0 and later enables the RailExchangeQuoteReq and RailExchangeReq transactions for SNCF through Universal API.

• For SNCF the customer must send RailPricingSolution in the RailExchangeQuote request.

• RailExchangeQuote without RailPricingSolution is NOT supported by RCS for these vendors. Therefore, for SNCF the customer is expected to do a RailAvailabilitySearchReq/LFS to get a new RailPricingSolution and then pass it in RailExchangeQuote.

• For an SNCF (2C) exchange quote:

  • RailExchangeQuoteReq/RailPricingSolution/RailPricingInfo/RailFare/RailFareNoteRef and RailExchangeQuoteReq/RailFareNoteList should be present.

  • Both should be taken from the RailPricingSolution returned in RailAvailabilitySearchRsp done before exchange quote

• SNCF allows adding new rail segments and modifying or canceling existing segments at a rail journey level.

Users can indicate whether to add/modify/cancel rail journeys through the RailPricingSolution and RailExchangeSolution element, specifically in the @Operation attribute.

PAO (3C)

Universal API 19.1 includes PAO (3C) regional trains as a supplier for SNCF in shop, price, and book. Customers who want to use it must be provisioned for the 3C supplier code.

To specify PAO in the availability response, you must specify it as a preferred supplier in RailSearchModifiers/PreferredSuppliers/RailSupplier Code="3C"

The HostToken in availability response must be used in the pricing and rail reservation requests.

With PAO:

• When shopping regional rail, service is returned for the 11 regions in France.
• When shopping, journey solutions return in association with a fare quote, as received from the 3C/SNCF Regional provider
• When performing a shop/price/book for PAO, an agent must:
  • Provide the origin and destination dates of travel and other shopping modifiers if necessary. For example, loyalty cards, discount codes, corporate codes, etc.
  • Be able to price a selected journey solution with or without modifiers i.e. loyalty cards, discount codes, corporate codes, etc.
  • Be able to select a journey solution and create a booking with or without modifiers i.e. loyalty cards, discount codes, corporate codes.

Notes:

• SNCF (2C) does not have a host token, but is available for 3C.

• Loyalty card is not supported by 2C/3C.

• Agency Mail ID is not supported by 3C.

• SNCF (3C) Does not provite round trip via Universal API.