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
- 840ae8488e4f8a4d849af3ae926085f2a24091d36317046aa8b901bdb19912df
- request
- e45405f4b9aae8213b29f5b43e7f30d0163edffa3fb3bbff77bda963fbac4961
- transaction
- 7dd9ba86b73ec3ec711d45c2dc340e52b87510c6a3c2144babbc62be7e31a0e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61066
the chainentry 61066
- sealed to the entry before
- 9b3b9f386a0ad85020f67e74d6e0b5e75e55613b31a3cdef095000664d12ac2b
- this leaf
- da17f6fca7f61db6a8f534d709fdf5677b930d80242a7ee8d88f4f2e2915c644
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F/ets10CndK3/aYMHdPGuKyVFr/JaLRnEG1LSEyk8/PaKl+EpMmaMvDKnnSWruH9plIndoRf89+p5clVoc+QCw==