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
- e52175f6bc4bf3763bc400ccc506001a29551aec029467c68c2c7a8494eb4f2f
- request
- 10eee804eb53d71988c5ff2b2f3781285b3bfad670d89381f8a93ba07bb37fa8
- transaction
- f8e3df5201d669edfd75dfadacc4dc4ac95e4bfdf65001d8229fc902929355b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16746
the chainentry 16746
- sealed to the entry before
- 97b26dbc830f793c00518ef202cfbad896c9e83d00aa6e8efa31854e829ac196
- this leaf
- 61b43f1076f4424aa61e177d519fd2157c048c39a6fac3d358ed26f3ce545943
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mGoTflmOgAS6HOCFhizvFaPagqo1t0v0uery47xWzYMPKA2uOLQpRyyIlHjcoZygCkh867O1n/SLMo7soWSaDQ==