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
- d0c4bb9db5bacd0c641cb863b618f743b380169cd20de6163942279b8a78e72c
- request
- 77128922bc83027c77eb0f4858b40f8d1cd48755332cac3ec0c33481cc6dbad9
- transaction
- b9c38e9d01fdd6b0c30a843eb23894b674968651ef7564b7013a8098784dc501computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72566
the chainentry 72566
- sealed to the entry before
- 2ac26caf46d7e26f1f038ca1a6631a90a9ecae9dd2d741734ec3935aef5c0074
- this leaf
- 371866def7077b3f615e396600dda8ad8c12698e104caba3a22584d96651d27f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +x8UahZbgdOs+OOcJV9LoC9kNjJmG3GaOAPFrRtJBPdmCjqtwMrKsDRejyTFRQNP8I8ibF9A/ez6ZhpUMqn5Cg==