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
- ba76f67cfa2b5fb09f73544ecbffb3ed07bc5a8ec5dc6933482704b3498e450f
- request
- 0aa555b32ba358d02790e06ccb179c4f3e936ba08d29d3de9b43407893b6730f
- transaction
- eee295f09070625834fa3141bdc5d0d59382e723e20ebd04c3f71ab98cad0837computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2715
the chainentry 2715
- sealed to the entry before
- 43e2281df9065c67747908b2d1f4cc7f26e2fbed0d96da42620812387c6cc92f
- this leaf
- 63a141a206eaf5e325344c7a3d565ac0cf744ae35ebf8ee62a9ce04258fd7f5d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xHPyNQAn0DYFPk9fgaS3bh4wdblgvoa4zmBbAY+jEtUUN7z9hMLaDSNbPvQQMAxB3Hqq0NcJR9pwp6Gy/Z5yBA==