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
- fbdb1735afc9e764917b06cbf03e8ea822d007c9abe35dc515b82186a3d7794a
- request
- 91dd4692f9588887a0f1052f4e4ea6920f3850779a16dfef305233a5b3985699
- transaction
- 6e9f6871e390cfba70f4f3d454163c038e629225f54bb17048d9b87fe7e76fc6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58369
the chainentry 58369
- sealed to the entry before
- c2a95e284cf4c3e4c9afd3ac1ef4848e047c89651ea0601eaa56143eef087bdd
- this leaf
- 547da4447daf99151bd646da8ecd67b39e83afe4e84c9d0648f2d3886bf1566d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4oNzBG0AEdSyPxVjsJDXwYrYX7dq12lVgbh138nhNQf2noYEdqIyyaDrbzCpj7GuBDiPP7f5KRXJfYqSjuNDBg==