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
- 25dd1840e0cf15a86ff4370631a9006dc80772a9e10df194ec9d516112471e97
- request
- 0c6b639c5aa746757cf6e7112bb4c97c2a2747c080974a1e0c00cd406cfdc7c2
- transaction
- e09b4e6b316d24d6f2f11238c3540f2bbede60919cf391ef7c0cacc59bf124b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17004
the chainentry 17004
- sealed to the entry before
- e770ac4a8b9b475f4730dae4b45d07e2690e610be27b34324e1408bbc8c8fc4f
- this leaf
- 08d810f826e8f3704ab12033f9569a9149573bdac6684d1e14c9c2e8d41df455
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bz24CBVoyJqcbH+C0XgVX6P0ZZV6WQ3c7scaKmwkDNNIgtpvzp0d7cst9V/pRi/SGO27vsqosF3MrH38wpVnBw==