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
- 1ec765377c0f8960d81667aca3e4803dfd734c20cfa7f38e905726477fa47d46
- request
- 1fdbcf828c7f429d8a5207faef85413011136ed2a1423e3c3e0b5cf233febc19
- transaction
- 5b4fad770cafdc704bf3162065071ddf3e877a729b177a05f0b3e9f436f92ce7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48489
the chainentry 48489
- sealed to the entry before
- 0b0c8a50eaab449574ff8dc71aed68fe6b31c8879fddb23402ce4210681b67c2
- this leaf
- be465d2d6b7735f62efcd6cca88d6288f451e676e48923695bab5eb664c05619
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NY9HnO3AQXI0mzv+p9Bbm+Bj1NW/j9nEp33c04KHvhiXGphgCfkrB9f0manyeYjOycHSpi/ZyXOnePdnbfL3Aw==