Payment Configuration
The payment configuration decides which payment service provider (PSP) a property's payments run through and how a payment taken by that provider is recorded in the property's PMS. It is the foundation for guest payments across the digital guest journey and for staff-side charges in the Operations Platform.
The Payment page in the Operations Platform shows the scope you are on and carries no editable fields. LIKE MAGIC maintains the values, so a change is a Support Ticket rather than a click. This article explains what the configuration decides, and each provider covered here has its own setup guide.
1. Before You Start
- Decide which PSP the account will use (see section 4).
- Know whether the request applies to the whole account or to a single property (see section 3).
- Know which PMS payment method a provider payment should post to on the folio (see section 5).
2. Where Payment Configuration Lives
The payment configuration exists at two scopes:
- Account: the configuration shared by the account's properties.
- Property: the configuration for a single property.
ℹ️ Neither scope is editable in the Operations Platform. LIKE MAGIC maintains the payment configuration, so request every change described here via a Support Ticket and name the scope it applies to.
3. Account and Property Scope
One payment service provider is enabled per account. A configuration with more than one enabled provider is rejected, so all properties of an account run through the same provider.
Within that provider, values are held per property. Two properties on the same account can therefore differ in how their payments post to the PMS while sharing the provider.
ℹ️ Note: Ask for the shared behaviour at account level and for a property-specific value only where a property genuinely differs. See Configure Property Settings for how account-level and property-level settings relate.
4. Choosing a Payment Service Provider
| PSP | Setup guide |
|---|---|
| Adyen | Adyen Setup |
| Datatrans | Datatrans Setup |
| Worldline | Worldline Setup |
An account runs on one enabled provider at a time. The enabled provider decides how the guest pays (a payment form in the page on Adyen, a redirect to the provider's hosted payment page on Datatrans and Worldline) and which mapping values apply in section 5.
5. Payment Methods and Mapping
The payment configuration holds two mappings that connect the provider to the property's PMS:
- PSP to PMS payment method: which PMS payment method a payment taken through the provider is recorded as.
- Offline to online payment method: which online method an offline or manual payment method corresponds to.
Both are maintained by LIKE MAGIC and are not editable in the Operations Platform. To add a payment method or change how it lands on the folio, request it via a Support Ticket and name the property, the provider method and the PMS method it should post to.
ℹ️ Note: After a mapping change, run a test payment and confirm it appears on the folio (see Billing and Folio).
6. Provider Setup Guides
The provider-specific details live in their own guides:
For prepayment routing (which charges the guest should not pay because they are already covered), see Prepayment Configuration.
7. Conclusion
Payment configuration ties an account to one enabled payment service provider and records how each payment posts to the property's PMS. The Payment page shows the scope but holds no editable fields, so decide the provider, know the property and the PMS method involved, request the change via a Support Ticket, and verify a payment reaches the folio before going live.