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
- 5efb158dff4fbac6225585e4706626ce48165613dd48dfbdc0ed1f605ff99d88
- request
- e226621ffa21f7f4f56daedf0d8b49311d97831e3c629cfb380a8a87bd7b36d2
- transaction
- 3a2cd3aa1166a79ab1028859e2291703b1b9451b00af4b6a484d949617f2dcaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66390
the chainentry 66390
- sealed to the entry before
- 76d90cfef8c83f70d55e9dc9536d88f3fb6bca784d552e21dc6534e9b64477a9
- this leaf
- 40117d294df0fef7c822a0547e56fdb94d318884ea490197655b11e2af44bf6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1qHNUqpzDk7SOE2wpTHLuDDcpINNrJ+417kwjxtllBtsLfX1EH7rmxSMJLwrsXO6XSB1d4148AAoMhK3hHPMAQ==