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
- 7641c8bc65c726ce0bde0b144cdec6eaaee1a5957368f0276d1713aedfaf568c
- request
- 43eed8ce893e7276678f4ea312b27bc0034076770047236a2ed0afe828f28054
- transaction
- d2aa759e9e7f671e41578f288a4a3fde761c353559f1f629787771efd453c7eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75249
the chainentry 75249
- sealed to the entry before
- da726b7f2e97b0547935be917923937eaecee476c8ca119bca871f39e6b50d83
- this leaf
- 63f23b70806c65060aa297651b1c1a2088a3a78397a34c647fd103504e360b77
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hQAaQQLNoaeuOQ7oTJw2GJJieRo0s9Kdv0piwu3scYjgzx5/H7XA5bZah997bf6Lx3gtVDUwaOtevxOESRr3BQ==