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
- a7abf661c681b10186eada659b81ae2fb11cf1f85458a841196e450b0900e4b4
- request
- eabe1b10b31b5144a38f85ab1566d8109acb624971ca49d81542adea603dc04f
- transaction
- c5a4ccc0d73b0f9eae06b68ceac77947967b636856820c38b496bbef40c89659computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36448
the chainentry 36448
- sealed to the entry before
- 03628fe6a22de3dfceaef66682fd800c65bdefe7b1cd6f4382c71cbb8ac91d4f
- this leaf
- 739970650d7a566be7c3a448a1ffeffbbf37293bb5695d030bf90170acd53063
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IB0uhOWCOcWXjNVSNO4xCQctc2UKOWDbw5gMaMuYW2dpgGMuXvt67+VASmb3VoKJTXdOtFgm5201MB5Ias1GBw==