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
- 2f743ae81a220a6478aac97e1c0cb4da44fa84c5944837a46a00be8be903ad6a
- request
- 1520b71de999c322f358923fa0fcfaed50930d2af0db53e9ee90678cb6bb8062
- transaction
- f59237310ce9dbd6756a1728ffbb090dbd13685d67290bd9cce65e1ce1d6fedecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59940
the chainentry 59940
- sealed to the entry before
- 390f8f20513ba0c04218c24f711292d6bc253dd76572ae585b8ea11a2f36a89a
- this leaf
- aa810f63e9c7e6012509cd3b610122630acb30c75fd2fd6453dd33005d94fb14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K5bdVds/86tdVzUkjKXhlHHGar+jnB6Gd9uCRMVXLlDj0ZhkgKcLCQBZqIc6XqtvmitIqxnSmqEerNBovuAEBQ==