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
- 03d89ab1bb3202b883f29f9d0219be0afb7d70d9be624d271e0456479423dbf7
- request
- a687da171593a8ee52b12d73dab3995c49cdf138be66af2d4acb3bb61dd21388
- transaction
- 983b4cbc0757979edac864ee4c2ff3ccad413e8ba287ea8214587856cac9d8b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37705
the chainentry 37705
- sealed to the entry before
- 71e734d3c62a7873364886bee43660704bea62f714b8cf7eda09447c80dec6f0
- this leaf
- 638b5f5e61874549e636a21b206e1327026f425b7053fc3b40e21ed18d7c7be8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dh04IbpIcaJKykhnQ9SdQnT+iu6da9gzZrgy4o/acobMf++4nurzziKrPgMaJEUdQ+6rUYvlSdPHNYILTuZNCg==