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
- aaf2ff327152490a7b159a570afb004610d7721bc99db70c0f629abd304658f7
- request
- 94fc1f9df3b2d16859df6dfbfac484bc3499d49f4fc42744a08ff2b0265d9f5d
- transaction
- 39506f007b307d8928de248f5cc34b416e06a17eb487f7e88fe092dd2da20313computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34639
the chainentry 34639
- sealed to the entry before
- 0456ceef5ce5b7a96e0cde400ad201f9064c4fc15a558909e81e94073b8d30cb
- this leaf
- 415339132d121d0654d6504d29925e3ab2e926cd30841f6e3e0c272040f37021
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S4qepKxBO8615uhx82mqdZKaQMAPHbbJ7JddhhTs26gX2ajpF1LvSvZP+MEhnM87W4RfpjjC+NlM+lM04ajuCA==