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
- f3ab04b26cce01978f12c86c6b1b9985e702eb4d22c267528c14732df1ad9be3
- request
- 100fee2329c7174a7e54ce029eb7a7005958986c129599318b7c8143a7620dbd
- transaction
- 5830d3bdaf19cd9bed7a6193339be08df36f21f50749637c8c9c43b9b1a2d7d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74657
the chainentry 74657
- sealed to the entry before
- 0793af4068a802ca923a347637df567cadb15e1da0c1b8413ee9dc85f330f5d9
- this leaf
- 302352087667645c48a3c7aaa4a7e452be686b17b31e3a0076b38901c8051018
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XdR5O54hZl/M6DF2wEhUybBzWQGJKjpQ01RVNnA2hvBJ6x3glZTuakl2DWbTi0JgZNfTeKcsS9F+lrHOi0AsAA==