Release note - v0.3393.0 ... v0.3394.2

March 30, 2026
  • 2 new features
  • 2 updated routes
Adding a new payment_method field in the payment status route response, allowing the PMS to identify the payment method used (Visa, Mastercard, American Express, etc.) during a successful transaction. The action_code field also integrates a new code for optional service payments. Migration of the product activities route to Quable V5, improving the quality and richness of the data returned (categories, sub-activities, equipment, services, availabilities, themes) while maintaining the same API contract.

Highlights

  • Added a new payment_method field in the payment status route response, allowing to identify the payment method used (Visa, Mastercard, American Express card, etc.)
  • Migration of the GET/v2/products/{product_id}/activities route to Quable V5 for better activity data management

v0.3394.2 Details

New payment_method field for the payment detail route

The GET/v0/payments/{payment_id}/status route evolves to include a new payment_method field in the response. This field allows to identify the payment method used during a transaction (VI for Visa, MC for Mastercard, AE for American Express, etc.).

This information is particularly useful in the context of PMS-side payment links, which requires knowing the payment method in the event of a successful transaction.

New field in the response:

  • payment_method (string): Payment method code (e.g.: "VI", "MC", "AE")

Response example:

{
  "payment": {
    "action_code": "PAYMENT_BOOKING",
    "channel_code": "CTA",
    "payment_method": "VI",
    "payment_status": "OK",
    "server_id": "EOGONE",
    "amount": "1234.56",
    "currency_code": "EUR"
  },
  "booking": {
    "id": "12345678",
    "bulletin_number": "12345678",
    "gm_number": "12345678"
  }
}

Updating the action_code field: The action_code field also integrates a new code: PAYMENT_SERVICES_IN_OPTION to identify payments for optional services.

v0.3394.0 Details

Migration to Quable V5 for product activities

The GET/v2/products/{product_id}/activities route has been migrated to rely on Quable V5, the new version of the product data management platform.

This migration improves the quality and richness of the data returned concerning activities associated with products, while ensuring service continuity with the same API contract.

Activity data now includes:

  • Activity categories (excursions, sports, services, etc.)
  • Detailed sub-activities with descriptions, durations, age restrictions
  • Equipment included or available on request
  • Associated services (lunch, guide, etc.)
  • Availability periods and opening days
  • Themes related to activities
GET/v0/payments/{payment_id}/status
See more

The response follow the model of an xmResponse with a finalisePaymentResponse.

GET/v2/products/{product_id}/activities
See more

Retrieves all activities a customer can perform.