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
- 4e25c4944e7fdfb985eddfc5bd9e83cdcce8381d5436d9ecf034a15f01fe93a8
- request
- 4376821f74ab7b2504c7e17d120cc23bec4537d81b0c6698e8f6d66df42e352f
- transaction
- f1c28fa233fab53972182c98d214e69e486915de2bbd2da5bf9446d22e5a63c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37842
the chainentry 37842
- sealed to the entry before
- cbfa7a94e00c8152bd47bd55bebdf8550c00064413fb86b4608545a306c93862
- this leaf
- 25534ef968c4356158caf87e70904fb4cd00f6ea79d980429e9c738fbe73822c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1UGCZ5gZow/2NhcJxcpkcw+RzHynMRfIpdKy4jJ5mcqzMHEvFmFCEowuzNJO1O9XM1lRJkn7Qiuymjugnr46BA==