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
- b3a86145946326e4d3e8cc0da2698fa481e5d8b763fc5947979276f8059c7b25
- request
- 19a2b3619ee1b1539686bc6cd71ab0cfdfcbc95be74ebde50fd8832748bd959c
- transaction
- 85ba873e3c2a8ff609f84aec0e1ce33fc62ebc626f5273dec6d65045211648e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24105
the chainentry 24105
- sealed to the entry before
- 58d29bc67affab54f263ff54206e97977332375022d4f204cb4e55a06de81a6c
- this leaf
- de43b57888215021c67298dab0656b0fda3fb428901de48f555c63341f988182
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dQYCF06b0rkZAyVqiF7OU88Ig9zNmOcSE7eO3dzOkeHHEVPXmoIru36o4jUoNK3J+3vudJghAzXEXigd1OlzBQ==