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
- 91a9a01d398654c65b7552bec9ff532a6b38115f3d31ec360b938c927becb9f8
- request
- 1ecd53a1aea444c93e9c74f1f3549eec339c889124ad7a063729d9f4f8be4097
- transaction
- 5eb5c3c5a2dbbdca20aeecc26b6fde8ce77e9e5478a6e60bb876750717266a05computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67602
the chainentry 67602
- sealed to the entry before
- bdfd278866c0a89796e45d0fda92a2d9b92ba72d0d3fe610e241ce1caa3a3280
- this leaf
- 24ad37c9fee0d25d6e75f4e6d5a55c03354f45db976a1e0455db2b1baa873a6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- taUd6REyAei+lKWwvVRYcYCJHQv0JwhzBNKiDBJzqa2i5KqqgoRw2xBDnAC3xNgQPjpJmSG14tv6NJ7h4gfBBQ==