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
- c3bab59c176cde7b0b0959dae33f14b894f28c8380c14da1642f3b75b406ae50
- request
- a94182515cc63d2b1dd61df874e126c5782403065aaf24ffed85f22c958d7c80
- transaction
- 40342bd3eeaa3beb784423ff1ae1adf37b2229a652e3cbe93f04162f91999fc3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36298
the chainentry 36298
- sealed to the entry before
- 635981fc253f4973e83d48f112f5a8b558d3dac56bd7e82047d03314e4ed736c
- this leaf
- b748c4dc770100172c15e1dccffda1d9937fb1556f226dc5abe2dc643c4e3075
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rtyGMOEd6nZHm6mR/IRw7Tb4L5vbQMWPCPf4hb1Yb04McKcxWC9MwfMIkDAQBao+Hqmp9ehkdvMBUDUQsI+hBQ==