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
- 6bd5958da3ec6d6b15d6bad27f460c05c796b35d8346e5c82e0624eb37395dc8
- request
- 355ce28d90974c3a8241e43c88f0eaac71b501122c60597cae09f9379b66132e
- transaction
- 82910d2d2ddc2ee51be219e233c20105496a222b1b15cab82831991a7d9868c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44403
the chainentry 44403
- sealed to the entry before
- ea36a27a7fc90ce894d7563b075e567bbaaed4c9d2721a32aad0c82eb41a161f
- this leaf
- 7259308d9e6f3185d8280987b0761b97cd50e0d2795868a03c1861501e79dbb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iYsuKis7fhXkL0Ef4WIy79kGn+oWWbFSpnuooFCYKAvqkmPr04QdnSxMYbTRbuh0/sr8y9HuIGiAwuxJ5jFeAQ==