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
- 26262af17ae03ec172c8eb197973ebdf47140a947d846639a5fa02e17618ff73
- request
- 8d74a2640b89112cbf9408ed8757d19d00711eb726407e3acf66a5439d97dfb4
- transaction
- 4eeb6f56f0c5a9721f70693362876baf18f9d83c3e18ff19a0108c6e2570a28acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41709
the chainentry 41709
- sealed to the entry before
- d455b987474679e2c82e2936fedc4896bcf1cee3eb9bb7a85b0cdd4844a94646
- this leaf
- 861386218fb9444618ffee23492c2bd2f781e2c5def2f936fd82d20f746d39d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IXA84fLdLYyXIAiCzMMj/LqKqJdScSMaY1Amkkve8BQGW3m+HSACcDBxLHCSrEsINQhRdR5zB3XNZTobd1ZVCQ==