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
- 2b545e2fb9397fc47b6fa4e6c096727f3df5b77b8535f9275ac85f7a99f6f64f
- request
- 7ee015680c03203b83cd6c7a0366a74d9e44c702f0493eea706103410504d449
- transaction
- 7236f17ea6743dc503a14496b249b13deee3526d3ae661b6598b021d31900c13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33812
the chainentry 33812
- sealed to the entry before
- f56ab7de1195693b59fa71474cb5c6e30a35164895c1ec945dc6120c00fa0efa
- this leaf
- 42a6abe71bce66eb53e3e72414cee7562dca69629f8888825a5dee1dc13a1f8b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pa34EbylzjGI1hDtBkph/xSYAChk4OHbzM5lxsUs+IQ09kmoo5cqy2SDVVu8/KkCCxmlLDcA6y6nnw6Bvn74Bw==