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
- d8c529139d419a137fac424e3071f4caba3780d9132a6230578a0344e5a13eda
- request
- 7248a92d8eee74e9cfba69ad1255fa6f820399b5bf243f9ac8598e83fc20ea7c
- transaction
- 61c2ce0b5c63671bd4d5c2af2dcadbfd4b23efc640d41a6bf19ac69656903fe5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69547
the chainentry 69547
- sealed to the entry before
- ad0f69eb5aeb5c8315215ee2d414899caa3dc04910a9253f8b89e36527ef9d5b
- this leaf
- ac3be6a0780dae348573c336c48583d593883e8eab2491cece5dd015d4d4a7bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4AkrPJq3c4rmzmE//Br/J7PM2Czxcm8dYZTIRSOy3pjRWfQGyUhAqoN31JUVNW9gA9n8JRwCM0oh/5pRlbtHCA==