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
- 84c91eb7bc7444682bce6d2f14c2158fd75967d17e9d22abf54112940ffd5838
- request
- 3bc963618e75fb16c95bf25a8e85cdf5b33db35669ebef3f7f57ca2cc9841aa3
- transaction
- 1b74f19419e4acfa46a92ea6f1b16c32894a158e14a739295f5f4000c149be3acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8101
the chainentry 8101
- sealed to the entry before
- 58f2b1ed78180f94ca01827f5d3a913cb78d5f688004ec2f80fc773c16b082e5
- this leaf
- f793a5b2672d8c70e68e0874383cc2954d7122698fabf70ee48146fd5b4354a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lKDrmBXTUdb2n4DvpKKi/HiP3dCyV8jzGQR+xZRokN/eyjWiGjt8bjXfnohHp/1hj7ah5SZ72VmIh8z19q47CA==