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
- 93cd697f9aa2c17d768fb364e626968f687423e54262e1ca84c874fd79e6850b
- request
- 3cb50f2ad1b2d113d0be613309e9234db9aeaa8ecd6b659eb107f61173ded0f7
- transaction
- cbc91822f65323442689467d03d07ea1213864c9d9c5cf5167b718b2f9dd10e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50160
the chainentry 50160
- sealed to the entry before
- be710fe76e71409e81ce781e9d11c1a75a1c741edf940e7705b991b28f45fa94
- this leaf
- 78ffecd9dacd2b8486e7b487d5ab3bd6c406d6f8c6d0c6a95a84432d7a6cae57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ii3v/x5hx7cP4BNs7VOLdUHf1Jgk5oJ2NYgVceRgQSXX2xsyP0LLhSYzCXu1C0HTMYDQc/pXSPqmj7nHu8YADw==