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
- a1d0a575d72ecdeefad4de546a867e34d6313f3a05863412b4562fb820959e1d
- request
- d28771bf583e93508ed45b257884300cd886f87739c962ad0fbcb47766dcb39d
- transaction
- d4f8e66bd20ba7e53e6c374925fa82a500b85f847868a7bbcd6e01add7fc9c8acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24613
the chainentry 24613
- sealed to the entry before
- ab4e68e47951704313bec8d9d824b65a57a75a16ea2fedc36d149ef5dcbb1be2
- this leaf
- 8f5927a839699594b3340b06778187f43a541583cc56ce74f2833c58e2473615
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dgQIIA1eCb9HwwLqNcuvXs/7J2U49cvK4WgoUcT0ytOvbtXXl5zasTJu7M35te9k+hBLlGHY7b8vM+XXom7cAw==