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
- ebea450d6bdc2d3fde09f5409051433fc4d7519953a87b43fd142390de21f3e5
- request
- 6cf0354b31d19beca2ddaa4f9200f177b54a7acc40f65dbb09f400d9358c121a
- transaction
- ecded425fc3cd515adb0895c3796a3ac8a2403d44718784754fdbcccf8015292computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56156
the chainentry 56156
- sealed to the entry before
- d399aeea3bbbf1c8fcd62e549586e2d8d679eba8e0b7defb170814850da44a83
- this leaf
- de1ae3c067646992b0c2bb6c3e04e918a6118dc1e773ecc000f351da72b1e710
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KVRp+qhf75DbqmRhVkkH/p3tlZjg4t1JUejABhT5ZdvEdDoyNI/PnkmIIQSjPm5SJJ4YOylWeA80mPalujdEBw==