Anatomy of a seal that wins a chargeback.
A cleanliness or damage dispute isn't won with politeness. It's won with proof nobody can accuse of being fabricated after the fact. That's exactly what Hostik seals.
The dispute you can't win amicably
A guest claims the room was dirty on arrival, or that they didn't cause the stain on the sofa. The platform opens a dispute; sometimes the bank triggers a chargeback. At that point the operator has two options: photos taken on a phone, with no reliable date, editable in Photoshop in ten seconds — or nothing. Either way, the arbiter rules against whoever can't prove their case.
The problem isn't the missing photo. It's that an ordinary photo proves nothing: not when it was taken, not that it wasn't retouched, not who took it. A screenshot of a shot the app "dated" is still a screenshot. The arbiter knows it, and rejects it.
What Hostik seals, at the moment of capture
When an agent finishes an intervention and takes the end-of-cleaning shots, each image is sealed at the instant of capture, not later. Three things are bound to the file: a SHA-256 hash computed over the exact bytes of the image, an Ed25519 signature that ties that hash to the operator's key, and a timestamp.
The consequence is simple to state: change a single pixel and the hash changes, which breaks the signature. You can't "touch up" the photo after sealing it without the verification failing. The proof is no longer the photo itself — it's the fact that it hasn't moved since capture.
Why it holds up before an arbiter
A platform or Visa arbitration doesn't ask for a legal masterpiece. It asks for a credible chain: here is the image, here is the proof it dates from the day of service, here is the proof it hasn't been altered since. The Ed25519 signature and the timestamp answer exactly those two questions, and a verifier can check them without having to take Hostik's word for anything.
That reversal is what matters: we no longer ask the arbiter to believe the operator. We give them the means to verify. A proof that verifies itself weighs infinitely more than a claim, however sincere.
Three chargebacks, one month
Over one month, an operator in our panel received three disputes: cleanliness denied on arrival, minibar damage wrongly attributed, furniture breakage that predated the stay. For each, the case submitted rested on the same triptych — sealed shot, timestamp, verifiable signature. All three were rejected in the operator's favour.
It isn't the win rate we remember, it's the absence of argument. None of the three turned into a bad-faith back-and-forth: the proof closed the discussion before it could bog down.
The margin it protects
A chargeback isn't just a lost amount: it's the time spent building a case, the risk to the host account's reputation, and the night that goes up in smoke. On low-margin short stays, two or three disputes lost in a month are enough to wipe out a room's profit.
The seal doesn't make disputes pleasant. It makes them losable by the other party. And when the team knows their proof will hold, remote inspection becomes calm: they no longer record to cover themselves, they record because it has become the normal end-of-intervention gesture.