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
- 0fd98de6c081449f853c08c642dcedf7028be7d6d6d237af52a4645a1f65b347
- request
- 8564103fdc1d6aeb5ca4191d0d1c1858abd91aece95657c9d5667ddcf1dd80ae
- transaction
- a6e6a87ba2bd1888fb76e162dcad1d889673b00c109f40e5fcaff22f41ce7d67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51036
the chainentry 51036
- sealed to the entry before
- 5d27491e3e28017710c5767e8c76fd5a3740fe9e1a8a39466f5885bb7210eef9
- this leaf
- 5354edbd5e0dff2f8bb91a90cb3ba29ffbae80f2c1340c25047dd284719de636
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DDUgMe9/wLQVs5VpUmy+ZI5IsZHBXfPX+cNbfgJ7n7HWHgkNXyFeVpKiX2mWVvvDiQmQZOZ/noqOpLbh8VDEBA==