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
- 18675b6f74403295f72ff56aefd63d333dec2ed1b49a8baf6726a7d2fc144622
- request
- 29caa2dd708485a0772f1edb25a3c8f520e70d4beb48669990f2146a51d74cd8
- transaction
- a87d3e678e4c098a60f47d324a21824158d0ee888942022b81ca4c031d0bb1d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67493
the chainentry 67493
- sealed to the entry before
- ce75fa3963a2522dcba2366e4cca8e5468df28823a3e23c1c840e766e2bc7293
- this leaf
- 155348b6655f9b8abe5de3d32b6cf122e8c589063a12fe1f37683a53a31c5939
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- egPt1eVlM3aYV2sYbKYK5yfCAsEtuhH5fL//qi/Sa2kje1KvesUBRclRF4CIEtNJ52XWl8REAFqXW6+FeVnwCA==