Skip to main content
There have been some updates on Yuno. Please check the updates below.
  • 3DS exemptions
  • First and last name optionals for Customer creation

3DS Exemptions

We’ve added support for 3DS exemptions to help you streamline your checkout experience while maintaining security. A new optional field, strong_customer_authentication_exemptions, is now available under payment_method.detail.card.three_d_secure in our Payments Public API. This allows you to define exemption preferences directly when creating a payment. Additionally, Yuno now supports receiving exemption recommendations from your fraud provider. These recommendations, as well as predefined exemption logic from your routing configuration, will be propagated through the full payment route to the final 3DS provider. You can now define exemptions via API or rely on your fraud provider’s advice—either way, the exemption type will persist throughout the flow, reaching the 3DS gateway and appearing in the payment response, GET API, and webhooks. For more information, please refer to the SCA exemptions documentation in the guides section.

Optional fields for customer creation

The first_name and last_name fields are now optional when creating a customer. If a specific payment provider requires these fields, we will prompt the user to complete them via the corresponding SDK form before proceeding with the payment. If you’re not using our SDK, please ensure that you provide this information at the time of payment creation, in case the selected provider requires it as mandatory.

Additional Updates

Endpoints affected

New fields added

  • Within additional_data -> airline
Field NameTypeDescriptionExamples
typeenumType of tripONE_WAY, ROUNDTRIP, MULTIPLE_DESTINATIONS
  • Within additional_data -> legs
FieldTypeDescriptionExample
orderintA running index (starts with 1), describing the order of legs in the same route.2
route_orderintA running index (starts with 1), describing the order of routes by time.

E.g: If an order contains 2 Routes:
New-York→London→Paris (connection in London)
• New-York→London should have route_order=1, order=1
• London→Paris should have route_order=1, order=2

Paris→London→New-York
• Paris→London should have route_order=2, order=1
• London→New-York should have route_order=2, order=2
1

Transportation

A new transportations struct has been added inside additional_data
FieldTypeDescriptionExample
transportationsarray of objectsSpecifies the transportations array of objects
idstringThe id of the transportation booking (MAX 255; MIN 1)AAA0001
descriptionstringThe description of the transportation booking (MAX 255; MIN 1)Bus ticket
typeenumTransportation booking typeONE_WAY, ROUNDTRIP, MULTIPLE_DESTINATIONS
legsarray of objectsSpecifies the legs array of objects
↳ ↳ orderintA running index (starts with 1), describing the order of legs in the same route2
↳ ↳ route_orderintA running index (starts with 1), describing the order of routes by time.
E.g: If an order contains 2 Routes:
New-York→London→Paris (connection in London)
New-York→London should have route_order=1, order=1
London→Paris should have “route_order”=1, order=2
Paris→London→New-York
Paris→London should have “route_order”=2, order=1
London→New-York should have “route_order”=2, order=2
1
↳ ↳ departure_countrystringCountry of the departure (MAX 2; MIN 2; ISO 3166-1)CO
↳ ↳ departure_citystringThe city of the departure (MAX 255; MIN 1)Bogotá
↳ ↳ departure_timezonestringDeparture timezone (MAX 6; MIN 6)-03:00
↳ ↳ departure_datetimetimestampThe departure date and time in local time at the departure2022-05-09T20:46:54.786342Z
↳ ↳ departure_referencestringThe reference of the departure (MAX 255; MIN 1)AAA001-2
↳ ↳ arrival_countrystringCountry of the arrival (MAX 2; MIN 2; ISO 3166-1)CO
↳ ↳ arrival_citystringThe city of the arrival (MAX 255; MIN 1)Medellín
↳ ↳ arrival_timezonestringArrival timezone (MAX 6; MIN 6)-03:00
↳ ↳ arrival_datetimetimestampThe arrival date and time in local time at the arrival2022-05-09T24:46:54.786342Z
↳ ↳ arrival_referencestringThe reference of the arrival (MAX 255; MIN 1)AAA001-4
↳ ↳ transportobjectSpecifies the transport object
↳ ↳ ↳ idstringThe id of the transportation vehicle (MAX 255; MIN 1)ASONDAKS-1234
↳ ↳ ↳ typeenumTransportation vehicle typeSHIP, BUS, TRAIN, TRAM, CAR
↳ ↳ ↳ descriptionstringThe description of the transportation vehicle (MAX 255; MIN 1)BUS 2022
passengersarray of objectsSame as in airlines
ticketsarray of objectsSame as in airlines