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
- ce95567eb439d097ed6a3645473834d61e893be7a1386bce956e9f9586afbebf
- request
- 1500d35084d901a7dbb3b775f4295f38a5cc73410ad3e25aa7b6f244e9c519e3
- transaction
- 841d86022041320767312db11d1e3ddc18d3ada2db0e313205cbc646b989f44dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16157
the chainentry 16157
- sealed to the entry before
- 4019c15f0bfdb843d9955b2879ddbdd3457b2c0f54ffc1c9a602411497f4c6da
- this leaf
- 13aa2c56b35bdd8a3449c3e7f41853ebae33983ecc563e88174eec7b52f9940a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oMzPklpbGf+ntMr4HNULeAUQVnKsi4Q0iBd3NJQEr3QVMjaI9NP5x6OqQdDvHBMpL2e16FNJn+zBCFYEYGxCBQ==