Summary: If your property uses Mews as its Property Management System (PMS), AXP is set up to work alongside it automatically. This article explains what information is shared between the two systems and what that means day-to-day for your team and guests.
Permissions Required: No specific AXP permissions required to read this article. Your Alliants account manager or support team handles the initial integration setup.
How it works
The Mews integration is two-way, meaning data flows in both directions:
Mews → AXP: Mews sends AXP updates about bookings, guest profiles, and room status automatically.
AXP → Mews: When a guest takes an action in the AXP guest app (like checking in or adding a payment card), AXP sends that information back to Mews.
This keeps both systems in sync without your team having to manually update either one.
What Mews sends to AXP
Mews automatically pushes the following updates to AXP:
Booking updates When a reservation is created, modified, or cancelled in Mews, AXP receives the update. This includes arrival and departure dates, room assignment, rate details, number of guests, and reservation status (reserved, checked in, checked out, or cancelled).
Guest profile updates When a guest profile is created or updated in Mews, AXP receives the latest details — including name, email, phone number, date of birth, address, loyalty ID, and VIP status.
Room status updates When a room's housekeeping status changes in Mews (e.g. dirty, clean, inspected, or out of service), AXP reflects that change. Room type and maximum occupancy information is also kept up to date.
What AXP sends to Mews
When a guest uses the AXP guest app, certain actions are written back to Mews automatically:
Guest action in AXP | What gets updated in Mews |
Completes online check-in | Reservation is marked as checked in |
Adds a payment card | Tokenised card is attached to the reservation |
Submits an estimated time of arrival (ETA) | Reservation start time is updated |
Submits a special request | A note is added to the service order |
A companion guest is added | Companion profile is created and linked to the reservation |
🗒️ Note: Outbound updates from AXP to Mews are controlled by a setting called sync enabled. If you're not seeing updates appear in Mews, check with your Alliants support contact to confirm this is turned on for your property.
How payment cards are handled securely
Card data entered by guests in the AXP app is never stored on Alliants servers.
Instead, it is captured directly by a PCI-compliant secure payment service (PCI Proxy / Datatrans) and a token reference is passed to Mews. This means your property stays PCI-compliant without any additional effort.
Common Questions
Q: Will I need to manually update Mews when a guest checks in via AXP?
A: No. When a guest completes the online check-in flow in the AXP guest app, the reservation status in Mews is updated automatically.
Q: What happens if a guest profile is merged in Mews?
A: AXP will detect the merge when Mews sends an update for the original guest profile and will merge the corresponding profiles in AXP as well. This happens automatically — no manual action is needed.
Q: Why isn't my guest's booking showing up in AXP?
A: Bookings appear in AXP when Mews sends a webhook event. If a booking isn't showing up, it's usually because the event hasn't been sent yet or there was a brief delay. If it still hasn't appeared after a few minutes, contact Alliants support with the reservation details.
Q: Why isn't AXP updating Mews when a guest checks in?
A: AXP will only write updates back to Mews if the sync enabled setting is turned on for your property. Contact your Alliants support contact to check and enable this.
Q: Does AXP store guest payment card details?
A: No. Card details are captured directly by a PCI-compliant secure payment service and are never stored on Alliants servers. Only a token reference is passed to Mews.