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
- 5ce553564da79ae2200e4b6a00ea7124fac5a94bba567d351a7e62779ca14b1a
- request
- b7d6ed0b2203ef396aa8f2400f8dd48b2cf7b50ad1f260980781ee74eb4460dc
- transaction
- 1b0f5cfabbac131dcb48e14fe64137d033abbc85e15be7b4e800b12deca19ec6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21953
the chainentry 21953
- sealed to the entry before
- 261fafe4c977295ecff3bd97d36509a44239ff543468f0d852812ca64593dbe8
- this leaf
- 7693b8e6a941985c31fca2013dc21feaaf912c1df3bd4092bf3c0eb085f58f65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KrQ8bg28Plk43NMlvqa4BS8169jzK5wXulWrC3UVPeiis9lCIYoyvzE8w0X8dBMqkMbi8kPZj6ZiC3LBgy4uCg==