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
- c9db736ea59f5fd787e8c1c393bc52fd95b7715ec199bebcb2593311b49e8961
- request
- e751043110b1ac78ec3a3c77508643b3451eb16a5b21c45a4e09e6cf77e7abd3
- transaction
- 9bb80faad30aa563f23d287408738c6b536a03855812d09921f99d05d5c0d90fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75981
the chainentry 75981
- sealed to the entry before
- 054a59927601d20c9079ebe7a37490029c9810f3b76cc43104547363eeda74b0
- this leaf
- 8b42d5bf884c3b4fbe72a328aaea4282c0f430c5f776823ef807889d0119dde4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dWG8eBMIJEBQ4RyOq6bOccfHGUVNqVuiYyheKuOzKudCWqPG7QSU7Gg6ak9QYP8rSR7zhKQSF//bf9GrF88lBA==