Case study · Payment middleware
Hostel20
Linking Beds24 and Worldline to take payment for bookings across a network of hostels.
- Sector
- Hospitality
- Type
- Payment integration
- Status
- In production
The context
Hostel20 manages its bookings with Beds24, a channel manager that centralises availability and bookings coming in from the various platforms. For payments, the network relies on Worldline. The two tools didn't talk to each other: a reliable bridge was needed between booking and payment.
The challenge
Payment middleware leaves no room for guesswork:
- every booking must match one payment, no more, no less;
- notifications from third-party services must be authenticated before they are acted on;
- a network incident must never lead to a double charge;
- no card data may pass through or be stored on the middleware.
What we built
A service that listens for Beds24 events, starts the payment flow on the Worldline side and updates the booking once the payment is confirmed.
- Verified notifications: every incoming call is authenticated before it is processed.
- Idempotent processing: replaying the same event never produces a second payment.
- Logging: every step is recorded, so any question about a booking can be answered.
- Delegated payment: card details are entered with Worldline; the middleware never sees any bank data.
The result
[To be completed: volume of bookings processed, time saved for the team, how long it has been in production.]
The middleware is in production and maintained by Kairn.