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
- 3f98ed721bd75361ce800b1071f8e1cd2f60bb5bbb671dd774b8c808d1d5ef28
- request
- 6c78fe4452051c28dfb05573dd9299f966461f66cbbda5c045f195261aead9bf
- transaction
- 3952ff224f47ad8c5b1550a3a044158be2ab5d8ef4b43dfb22c5ba81220162c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61611
the chainentry 61611
- sealed to the entry before
- 236345f8d6f2804ab43da2584fc94f7c0ea1d7f65ad68af52371c65afadd93bb
- this leaf
- 7c0c3916a4d6faaf7c2eed11c8cd40a2c2bf3b9eba1b1d0b7ce2f778af8b39ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mzR1mI+RaZT16TyzcJGhbR7yYY9pEn6S/NWYcog8//VHYx7PKWRRD5toBzpqS5lKlY5Pqcgcvw/9B/icGejEAg==