PrototypeBuilt by Tally Digital for SNAP Rentals. Fixture data, mock reservation system — nothing here touches a real booking.

Customer portal — working prototype

Your booking, without the phone call

The MVP from our proposal, running. Real code, real failure handling, a mock reservation system standing in for RCM.

Or send yourself the real thing

A confirmation email with a link straight into the booking — the way a real customer arrives. No account, no password. Open it on your phone.

MockedWhat is real here, and what discovery settles

Real

The tokenised link — payload-free, single-use, expiring. Burn it and it stays burned.

Stand-in

The email send, and the booking behind it is fixture data.

Discovery settles

Which system sends your confirmations today, and whether RCM can carry the token or it is attached downstream.

What this is actually showing

01

Getting in, safely

A single-use link that carries nothing in the URL, a code to the address already on file, two levels of access. Try a reference that does not exist — you get the same answer as a real one with the wrong surname. That is deliberate.

02

The shuttle, linked to the booking

Your own booking widget sells a free airport shuttle. Today the request form has no idea which booking it belongs to. Here it arrives carrying the reservation, the flight and the terminal — and it needs no third-party API to work.

03

What happens when RCM says no

RCM returns errors inside a 200 and does not lock rates. Add an extra, then make it fail on purpose. Nothing is charged twice, nothing silently succeeds, and the pending state is visible to the customer.