Trust and security
Built to
be audited.
Somebody hands a stranger a key and a card. Here is what happens to both.
Where the card goes
The number
never reaches us.
Card details go from the guest's own browser, or from the tap on the valet's phone, straight to Stripe. Valletto's servers are not on that path, so there is nothing on them to take.
Your company receives its guest payments through its payment account. Review the applicable processing fees and payout terms during setup.
Both ends of a session
What the handover
writes down.
The car is photographed at check-in and its plate is read and kept as an image. Every status after that carries a name and a time: received, parked, requested, retrieved, paid.
Two more are per-location settings the operator turns on: an odometer reading in and out, with a mileage alert threshold, and a damage inspection that has to be completed before the car is allowed to move.
The record
A protected history
of the visit.
Your team can review the visit from check-in to handoff, with the people and times attached to the work. A clear history helps you answer questions without relying on someone's memory.
When a time is wrong
An edit is an entry,
not a replacement.
Times do need correcting. A guest really did arrive earlier; a clock really was off. The server does not treat that as a privilege, it treats it as a record: the reason comes from a fixed list, the old and the new value both go into the session's log with the editor's name, and the managers at that location get a push.
A session that has already been paid refuses the edit outright, and a future timestamp is refused at the door.
Who can do what
Hiding a button
is not a permission.
Access follows each person's role in your company. Your team can see who may perform the actions below.
Personal profile changes do not change a team member's role or company access.
When a charge is disputed
The evidence
assembles itself.
A dispute lands from the card network and the report is generated on the spot, before anyone has been told. It pulls the charge, the session, that session's own event timeline, the messages the guest was sent, the car photographed at check-in and the device the payment came from, and brings the available visit details together for review.
What it does not do is guess. A fact that is missing has its sentence left out rather than filled in, and submitting the response to the network is still a decision a person makes.
The rest of the operation
The same platform,
seen from five sides.
Everything above is underneath all five of these.
Your IT team's list
Send us the long form.
Property IT, associations and procurement: we answer security questionnaires directly, and we would rather answer yours before you sign than after.