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
- 5a89004458b12cde2bcee895492558b0695ec64213be26087bc6d6f6b2b75f22
- request
- 8c52d239cc3ba5a70541195002310ef5371fe3dd97fc53334b407e1275b22be3
- transaction
- a1de0e1382d324d420049866e6e8b28ced498c72b27a95b0141792f29c31c2b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52926
the chainentry 52926
- sealed to the entry before
- 856356add41e74dd5f8a25121ac205383133440b701c83f9d6cf41edc246b6c3
- this leaf
- ab8fb18bde3b7b66bac8e99cf44f583adf640091e5f5e991ffd2a75e950dafaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5ELKhpQKHKeUTRWZXBm+Coi/eRpIfotQbmRa9weGuR2WoeKYxK19+1LYftJgNia07Ec408OrJC/MRpzrm1QOAA==