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
- 2b851ef122e9ddc32d9f9beca748284157bcf238126d478663bdc481ccebcc01
- request
- 827e2bdaa9b877ecf455db0c455e7f69f57c61fb89ad1114c3e82b70bc6bec10
- transaction
- 96140c90dd63ee9084beb4ec98e2401ab97cbcf4b69b285f7faaa19e7a34557ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69242
the chainentry 69242
- sealed to the entry before
- 1a433918ffec5b36ae06503671c8ac676cf480e0b3282ba482d6bd458c8a179e
- this leaf
- 9b254547f528841e7b5996f5aee13458ba85277bd16be9facfe72703ea98627b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yg3xxIYzzjoVTPYnNe6dzkdql6kyVNZodKrsTpQRQtzoPkCxZqpe7WH1bcplzFjVFko1MtHAttGTpbCXeV3MBQ==