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
- 78dd4ab71667dd653a1616bac449e587c5bb986e19b08de1bf112d0cc4029a72
- request
- 3b1c52c28930c86db8b7ed64f7d4b1df0b86247e87e713bf8b8048549b6fa321
- transaction
- 7f07cc99a84293671678d529d0c002a37a69b74a8c00f76e95a757c8bc90e06fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2580
the chainentry 2580
- sealed to the entry before
- e3c946902b786ef686fd15aff12134bea8ea507fe120b4f98776ab07c7fa6c7a
- this leaf
- ace2a4871d3710aaff29b00e44fa990d24202a47ef394fdcb3dde8b6946637ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qYoRWF9KmzcPpANacIaJYnXSkkjEgoRc5CJZd5l87z1z0FFrCksM/PIrpzM0yBYWkt8JccejgAsVu0ijIGbzCQ==