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
- 9722a5af379df71d7e910d631e405621103ab7133f7a6b4cdccb8a4330d2a89c
- request
- 1c6a6cd53145f2939e8ae713281f6e5a21af982ccfff343363bcf49ab6f4d686
- transaction
- d10b7efb554fb4821a2f8ad64f2bab996824982024aaf0e82ad14885d53b822ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69948
the chainentry 69948
- sealed to the entry before
- d11ce1f7fea9d27c17dd1a241c18429f4f912d6385e5d1a857ea6bc46a0f6146
- this leaf
- aa20d0b9704ba4ae177f1fece07f99031c0e314e8f6de95be64b65f5b252dc88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HgR56azS8rDfanh4q6DPpgJa8d9byiqdqZ+M9mveLci384YhKVqktsR52RJM3Ge1v9PRC2qKKrBs7Sp/1aC2Bw==