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
- 09d2bee667ebbcea6688ed0469fa31fbf652ffa04d1b43a59d392d9079752589
- request
- 816474dd272947c7441dc7a7be3297f7e68149de140cdacc7b2e1bc9a4a83e76
- transaction
- 8ee0c8dbb72fc0e5ac14f4b2c6fbe2f5503897221b4bdfffb94fe4a5b91cb48dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39342
the chainentry 39342
- sealed to the entry before
- fe6ebb974115a3f32397aa7fa1eec18b8064f468576245eab5ac2eb042a60880
- this leaf
- 23bd780b209964b1fc811540ee8007153e892a85e97fd2cef7377cd6f5e54ce2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SocLw2QMQ09OomujgX+sOKmM+EbzdQRcCnBNVK6Smp5jxxi6HL0VgAC/LJ24ODRKUMvKaXwhwPglw8bbHwJ7Dg==