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
- 743e04f5120faee36566af45bd785b532fa7a09323f3a51b1c95274db979f066
- request
- abe226a2ed3f414d532e9719db50272874af91ab5130268f612286db5b95d38a
- transaction
- 96b6ca5ee157b0133d71e2e9d600aa0b2d470576a84d5e163778a79806fe02eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30749
the chainentry 30749
- sealed to the entry before
- 92e8566e48b8194ad0efb76375fa34c2276320c531fecb9778f584b1bd8e92cb
- this leaf
- 10a4f51398c96cb3a1ec1d771ee18382243bd50883b33ea8d114870913227908
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fKOw7/Z5RwetaZj1/VSCWQAoNSo/wcOt+Xu/+nR14076rPiI0R3FILnoxEP2iwfiDoqTaXrwXFZgBx17qiQOAA==