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
- b6af789adce75d15fb2d465ff7d78e9528dbdb8a9b732e48cef47e4b540786bb
- request
- ab2aefd74d76506be14a11056a3fc1090e0e1ab208ab15a3cab9bed5c95ba4cd
- transaction
- 8724c7ce28735cbe27c0afc646335b06a031088e2e62f0be90c543ebe906e2decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66703
the chainentry 66703
- sealed to the entry before
- a137d16c7178fb16a730da6d901dbdba2c33e83955268b517224e5e31dd1c15a
- this leaf
- 86bf729439bd39291da13475640352efc8d329eafefe185fb6121614f5235b4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +3cdJuo06kT+SnYdboA0l4iB9nnybQbGr/zxxOILnmCBTwkB/mnlQ8dH5plcIz4mRv9mZ4Ny6hVH1RsslqoyCA==