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
- 8864665bd450003c18a4f77c6d9657e8dc0b9b4c8bb99bbcd4c1d45bbb7fd718
- request
- 0620f00401d81e6f8af9922ebf12a757c1fabd407cc26e8fe81f5d21fc878e41
- transaction
- facb043d79259e36f445009b81af3de8411a14f85ed9184598a6e6360c31410fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59476
the chainentry 59476
- sealed to the entry before
- 7ef52b686a47a70e9842bcfb9e526cbf95834f80c92a7cbc02d97bbbd1fcb5cb
- this leaf
- a69e28540c7a0361947a2839a6815a62f26403356c5c34f7d35b9bf7d7153354
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5tyOSZ5C54nYH0RahUpIOMKVl9zUlqBqFeBWqddGmDLXN3cbmDTwbA/jxhCYPgeMJpJsbexDgcLEo2Wy1S5qAw==