Skip to main content

Adyen Setup

Adyen is one of the payment service providers LIKE MAGIC connects to. This guide covers the Adyen-specific part of a property's payment configuration, so guest and staff payments are processed and returned to the folio. The shared part is described in Payment Configuration.

Neither part is editable in the Operations Platform. LIKE MAGIC holds the values, so every change here is a Support Ticket.

1. Prerequisites​

  • A live Adyen account for the property or Account.
  • The Adyen values the connection needs (see section 2).
  • The property's PMS connected, because a payment ends up on the folio in the PMS.

ℹ️ Note: An Account runs on one enabled provider at a time. Use this guide when the Account is on Adyen; use the Datatrans or Worldline guide otherwise.

2. Connecting Adyen​

The connection is assembled by LIKE MAGIC. Request it via a Support Ticket and name the values below.

At Account level the connection holds the Adyen merchant account, the API credentials, the client key, the HMAC key that Adyen's notifications are verified against, and the environment (test or live).

Per property it holds the merchant account (with a sub-merchant id where one is used), the country code, the default currency, and the list of allowed payment methods with a separate list for the Self-Service Kiosk.

3. Notifications​

Adyen posts notifications back to LIKE MAGIC, for example the results of authorisation and capture. Each notification is verified against the HMAC key held in the Account's Adyen configuration, and the result is then reflected against the reservation and its folio.

ℹ️ Note: A wrong or rotated HMAC key makes LIKE MAGIC reject the notifications, so an authorised payment never posts to the folio. If payment results are not appearing, the notification path is the first thing to have checked, via a Support Ticket.

4. Payment Methods​

The payment methods a property accepts through Adyen are part of its Adyen configuration, as an explicit allow-list. The Self-Service Kiosk carries a list of its own, so a method can be offered in the guest journey and withheld at the kiosk, or the other way round. Which methods are possible at all depends on what the property's Adyen account supports, and how each one posts to the folio comes from the mapping described in Payment Configuration.

To change a list, request it via a Support Ticket and name the property, the methods, and whether the change also applies to the kiosk.

5. Verifying the Connection​

  1. Run a test payment through the guest journey or a staff-side charge.
  2. Confirm the payment is authorised by Adyen.
  3. Confirm it appears on the reservation's folio (see Billing and Folio).

⚠️ Note: Verify a full round-trip (the payment and the notification that posts it to the folio) before the property goes live. An authorised payment that never posts to the folio points at the notification path.

6. Conclusion​

The Adyen connection holds the merchant account, credentials, client key, HMAC key and environment at Account level, and the merchant account, country, currency and allowed payment methods per property. LIKE MAGIC maintains all of it, so request a change via a Support Ticket and verify a payment reaches the folio end-to-end before going live.

Was this article helpful?