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
- 2d426237cc8ca11784d99095decc156ab440456ad35d2707ad53099bd588d6c2
- request
- d28f6463d3998acb54a664febdf2e19c696e32d4e9e8d84d103ec772a5cd738a
- transaction
- 5446f79487870065d094d70f6658d5dfc71ea8f11c7ea133efa83c8ba5cf533ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66856
the chainentry 66856
- sealed to the entry before
- f7a3b072956c7c1a883126549d56e4d2ef155ff291b95b11ddfd7dd620577beb
- this leaf
- 00cdebd301928867fcf5f9a7c507766eeecc8ea3d4d6249645fd91d4593b17b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MWdFMC/xuPI7TTOyN88Tw9gT6EMU3PmsCULl1kjpLhmA8AGjxLydIvQWfEDO9+KwZpTbRJwvmLk4+KFOMuUZAA==