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
- 84001e6a92e958790b1e78c5e152fa1854baad98a105146245e4b2172d37debc
- request
- bf6818b5be1e3708c73daae3912617f1421b74ee66ba9a225947749c6e0a9d16
- transaction
- 8acaa5577d2e0204b610ee45d958ff7365730249116016be42c46dbdb11929a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7858
the chainentry 7858
- sealed to the entry before
- 45255dadbd6c07bf156ff3381c58f2b161b380314e0e196d462687b3d1d4a8ff
- this leaf
- a3f69ed5b4cbe4a4a78e749163563d1fee7b88e0a1fa72ab165b12f92a085956
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MJsaYUaDttO7Xdok8DMZJsoaYXdXQygCpUCjJNR6iEgFGbw2HvzKSKjYaCbz2AYCHL25jGG9Q2iXVN6ox3pPBA==