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
- 60cee7a569a82de155d06a9af5416db9f1e091af1dbdf85de2118d5aa241d7cf
- request
- 0a8624020a43b6f0f21ed3ab057ac2080e80a38dfc297d8e183c4077b1d197de
- transaction
- 820725bccd65c918144c84a7fcb60ca44f8904e82957854bc73edaf503fcfe02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32901
the chainentry 32901
- sealed to the entry before
- 68e0bb57840c307cea3c3a5880bc310bbcfe36fb3a6c486da11eab950b722dd3
- this leaf
- 3f5713d8c7933ae0541aa04e43bd3e61130b0dd58fb866621a7c003bdfb9037a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fr9kwatODelTw/Tixtv5MKWKlQnIjil7hqRDr8b6PU/ApBp5glSCrFC9u07y/hGgdLycv8suW0NKVncrivZfAw==