Shane Murphy: Designing a Clearer Bahamas Travel Payment Journey

By Shane Ian Murphy | Global Secure founder commentary

A travel payment journey begins before a person presses a payment button. They want to understand what they are buying, what it will cost and which balance will be used. I use an invented Bahamas travel example to think through these questions for Global Secure product design. It is a design exercise, not a claim of a live service there.

Imagine a traveller reviewing a booking while away from home. The displayed purchase price is only one part of their decision. If a proposed service involves a conversion or a separate fee, the screen needs to explain that information at the point where it affects the choice. A later receipt cannot substitute for clarity before confirmation.

The source of payment should also be visible. People can hold more than one balance or connect more than one payment method. A familiar currency symbol is not enough if the user remains unsure which account or balance will be debited. A short, explicit description can prevent unnecessary uncertainty.

The confirmation state deserves its own design. “Processing” should describe an actual state and provide a useful next step. If the user is told to wait, they should understand whether it is safe to leave the screen and where to check progress. Repeatedly pressing a button should not feel like the only available response.

Recovery matters too. An unsuccessful purchase creates an immediate practical problem for someone travelling. They need a readable explanation, an appropriate support route and a way to distinguish a failed attempt from a completed payment. That information should be accessible without forcing them to reconstruct the entire journey.

I would test the invented travel journey by asking a participant to talk through what they expect before pressing the confirmation button. Which balance will change? What amount do they expect to see afterwards? Where will the receipt appear? Their explanation can be compared with the design team's intention. If the answers differ, the screen needs attention even if the participant completes the action successfully. A completed task does not necessarily mean that the person understood the decision they were making.

The review step should allow correction without creating unnecessary confusion. Someone may notice that they chose the wrong balance or need to revisit the purchase details. They should be able to understand what will happen when they go back. Does the proposed journey preserve their choices? Does it clearly show a revised amount? These questions belong in the walkthrough because a person deciding whether to continue needs confidence in the current screen, not a memory of a figure that appeared several steps earlier.

I would also examine the same journey after a short interruption. The invented traveller leaves the screen to check a booking detail and then returns. A useful design tells them whether they are reviewing an unfinished purchase, viewing a completed action or starting again. Without that context, the user may repeat an action simply to recover a sense of certainty. The design exercise should focus on making state understandable rather than assuming that everyone follows the sequence in one uninterrupted sitting from beginning to end.

The receipt can then be tested as a separate communication. Give it to someone without showing the earlier screens and ask what they believe happened. The description, status and relevant amounts should support the same account as the confirmation journey. If the receipt introduces unfamiliar wording, the team should check whether that wording helps the customer or merely reflects an internal system label. A consistent explanation across review, confirmation and later reference gives the person a more usable record of their action.

For me, this hypothetical Bahamas purchase illustrates why product design must connect the beginning, middle and end of an action. The useful question is whether a person can understand what is happening at each stage, including the moment when the expected path changes.

Disclosure: This founder commentary was drafted with AI assistance. Illustrative cover photograph; it does not depict a company project or asset.