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
- 6743b4b977901c35de1003d53569f6e944b4076a19bc3833334fc078142c287d
- request
- f819efec6d0cc54b554c93bc04afda2d8a03a4d4919a786dd44a2a45656bad02
- transaction
- 1c1b90b9f39af475913548a84492e3a1428060a3b98ba9e6fa19b649b10f83decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64756
the chainentry 64756
- sealed to the entry before
- b4b5880c1ced5c48871c2a5cd0ebbccbe224e9d1aa8c2c97cb3816fb51c75938
- this leaf
- 6de87d7d5dd5025e36ded5c63e8e19fc912766de8c51df1c43201825d5e67d46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OJbCIX6LKoiHdRrSUtu1z/Kf3SW3kC+psth4/Z42EsSHwxd0IzsWnKKcSsJVCVskQlM+uFGsmsrJJ2amMhK4BQ==