Some actions in the Manage My Booking (MMB) portal may require the customer to make an online payment. This FAQ explains what happens when the customer is redirected to an external payment gateway (e.g., Stripe, Adyen) and then returns to your website.
Why does the confirmation step open in a pop-up after payment?
When a customer completes payment through an external gateway and is redirected back to your website, the confirmation step of the MMB flow is always shown in a pop-up, even if the portal was originally opened in embedded mode.
This is expected behaviour.
Reason
To ensure that only one instance of the MMB widget processes the payment result.
Without this safeguard, multiple embedded elements on the page could attempt to handle the confirmation at the same time.
Does this affect how I implement MMB on my website?
No.
You do not need to do anything special.
The widget automatically switches to a pop-up for the final confirmation step after the payment redirect.
All other MMB behaviour—embedded rendering, pop-up rendering, configuration—remains unchanged.
What will the customer experience?
They start using MMB (either embedded or pop-up).
They begin an action that requires payment.
They are temporarily redirected to an external payment gateway.
After paying, they are sent back to your site.
A pop-up appears showing:
payment confirmation,
updated booking details,
success or error messages.
Can I disable the pop-up and force embedded mode after payment?
No.
For security and reliability reasons, the confirmation step must run inside a single, controlled instance of the widget—which is provided by the pop-up.
Will customers lose their place if the pop-up opens?
No.
The pop-up continues the flow exactly where the customer left off and shows the final status of their update or payment.