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
- 624c817c877010bb6e791dda704ae44c679b71504c8173801d3c4c92defe5bb3
- request
- faeab37b9d5a976c34eeea54a611f64cf6263919fa4a0ea3f1d0a8abe82bc59b
- transaction
- a546e12f5887f067e0d876aecd7e22eaf69d913aee4c36ad4fc026977c7e9a0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61023
the chainentry 61023
- sealed to the entry before
- 3d6af4db6aa87fd4306e87869562a9c483f490fb06bad4739c7ef9d5304989c4
- this leaf
- cee6cbc466a642316561c25b710882e4376de85330cf8956fa2a6142bf1c91a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S8uTQi+BFwmmTFNrynB2ALUVm7+YzoxC5QPxibf154dTwUpMBVYnigAKUspVuksskimbZ6TKnFUSUwuC4MydDA==