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
- 33a257c191fbc15e5f633e4961d4975ebe2d5fff9b1030a2b5cecd7e2b85cd8d
- request
- c8b40141af9a1c511606d6cd291596dc05825321f0047e0d719a59f1a6dd67b7
- transaction
- aa341f288c21d9b700b452bdf5d404dd56e6420877395851336c3a720e03d89dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76110
the chainentry 76110
- sealed to the entry before
- 2bbb10d436ee0579aa87a9a673663d202577b091c2e8940931aec5b35cf236f9
- this leaf
- a4481d5f470bb1b4b0478c03d42c27b9a621246934e808bc6a3b1c8f8ae82db9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T5jko/BXUKKv91xhyQld16DJBLK36n+DZUi86y6bljv8A+OECDZbEbPjcY2rUwoFSIfCmRKnAO1dgfS3iFu5CA==