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
- 5c20e0ced15de521ac30ef86119cfeef3973a5cc910a42b4d3cc594e140e97c7
- request
- 4f5bbdd7ea53525b92b2472a98e47756a74945c89951d31532acd5ebd3528e2b
- transaction
- 9ba7e6e1ea699217fbb93c539cfe2a70de6e441c75cd9050e7c677bb0ad12052computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27462
the chainentry 27462
- sealed to the entry before
- 01b7cb46d4b70d8859313d4cdb9f01fab6f6db327b6873e81e6125c9019b0c31
- this leaf
- 2b084140fe07aa296858f2008ee1d9fef4c983394b59eea2025c64f4c2253f86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Rj7QsFJGCOTi17U7Ru1xnotMblWtuShV+PSpnuV65N/KodLLDrFX1Nh7PPS6xPGuVrA6pXKzaksJTkAlKFbAw==