why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- b087837ed5d8c709a1bedf10b4363d2c7a230f3a8a42570f2c241b2c40ac687d
- request
- 15490cc084e4de9a525bcf6c9ec006e6ef7a911c3bbf91d524a0a1f405d1f88c
- transaction
- f30875cd2074197248927b8cc274571c51fa1111fb6b2167de47d24b9abaaf4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28957
the chainentry 28957
- sealed to the entry before
- 5e6d144d7732b47cc514cc5b0af8ace04e95a3aa71725a298f589833d4b937ae
- this leaf
- bb82533b61c53159d680b797ad4c971d0d155233b4a8d88e3fca69f895150615
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZTDDQSseYu3WTNF+cuHdTTdYWJMk1+HIiN4WegxiDOxJAmnPq+5mk43HoNU5gSTtP8MkXfGuhF4JMo4Uby+tAw==