Hi everyone, I’m Chris from the Customer Success team. 😁
I’ve been looking into the Checkout SDK by Mews Payments recently and, honestly, I think it’s a pretty exciting topic. So decided to share some insights here!
An SDK is, in simple terms, a ready-made toolkit for developers. Instead of building and maintaining the entire payment experience from scratch, a tech team can add the checkout directly to its own booking engine, app or guest journey.
Here’s a simple example:
A hotel has its own booking engine. Today, the guest might be redirected to a separate payment page and only be able to pay by card. With the Checkout SDK, payment stays within the existing flow, with additional options such as Apple Pay, Google Pay, SEPA and iDEAL. For the guest, it feels like one seamless process. For the hotel, part of the payment infrastructure is taken care of, while the payment is processed and reconciled directly in Mews.
That’s what makes it a game changer for me: it’s not just another integration. It’s a way to create a better guest journey without every tech team having to reinvent the payment wheel.
Have you run into this problem in your own integrations? External payment pages, missing payment methods or too much custom logic behind the scenes? I’d love to hear what takes the most time and energy for you in the comments. We all benefit from each others input here - don’t be shy 😁
If you want to see how payment can be brought directly into your own guest journey, which pitfalls to look out for and where you can avoid unnecessary custom development, comment DEEP DIVE. I’ll share some more concrete technical learnings.
Have a good weekend everyone!🥳