How Connection Works
Connect to the traveller, with their permission
Wallet Connect is how your organisation connects to a traveller’s Tripicon wallet. A connection grants nothing by itself; the traveller decides what you can see, for which trip, and for how long.
Illustrative example of the summary a traveller approves.
The traveller’s side
Nine clear steps, then Allow Selected Access
Every connection follows the same flow, so travellers always know what they are agreeing to.
- Introduction and sign-inWho you are and why you are connecting.
- Purpose and tripWhat the connection is for, and the one trip it covers.
- Information and capabilitiesWhich details you can see and what you can do with them.
- Duration and consentHow long access lasts, then a plain summary to approve.
Safe defaults
- One trip at a time.
- Read and suggest only. No direct changes to the traveller’s wallet.
- The shortest sensible duration.
- No documents, ever.
- No “share my wallet” button.
Pause or disconnect
Travellers can change permissions, pause or disconnect at any time. Changes are immediate.
Activity log
Every connection keeps a record of what was accessed and suggested.
Suggestions are reviewed
What you send is a proposal. The traveller accepts, edits, saves to one trip or rejects it.
Connections are in development. When a traveller revokes access, future access stops. Data already provided may remain subject to your own terms with the traveller.
Give your travellers a wallet
Tell us who travels with you and what you want to do better. We will show you what a program could look like.