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
- f7ce0d81f16d56b6a5f3c6c8581de71cd8147aba352cd261c0c0052a737fa75f
- request
- 8c0978b7e7fcde11dcc58dc8547794722d3b1f558e5b350ef5b26f9bf0b00aba
- transaction
- ff04da7d44f8849f594e88ca3ab20f8bf1da125f915d3754ef9c45e701910c39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20387
the chainentry 20387
- sealed to the entry before
- f6ae569c47ee1305bacea605da387d1c3b91f5a58e1480d3f7795e794e3836e9
- this leaf
- 6988f5de5071fdf67926568f9040646df463d35ad1eda901fde37e173eb3c2bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2dJdp0VclD+aqCwYynHmf4Hqio1t+uv5CitycvpWw3nTKDfj/iYofRmVtKp0tJysG9k+tN5IM1Nuu3cEHYx+Dw==