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
- 10abf394a87e7603fdda2d9c419091b9494f93c8def4373c6f8a54a126084d30
- request
- cd9b00870b5aab0189eaad616ef519ad2ffa264b0d4f21c204d7218c0a902fcc
- transaction
- e041ffda9f66a8ceb45523e47af1db293242743e85cda968c7fce02174069707computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59567
the chainentry 59567
- sealed to the entry before
- 0fdb235735ce30cbcfc8b215abb988317d4edc3d0f65778a0066a31607bf245a
- this leaf
- b2cddfce664636a2de51b33d3773405557ffd497acb434cff3d40b319bbd464d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aWR7+HNW8CTcbXbzOO6abrT2ohQLevnmJgc7yWf442p/oXbhHHAXAUFjzB3vSJwHZFZNo7tgpjOnsEmI8QJUDg==