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
- 36de4963fd19257b62e832307df508bcb330ec0dcd4ac716cb134422b9de5c1c
- request
- 96eaa141ad899a80680a1e80873bbdbc15129eb3012d4c31cf10bd96fd9cb4d3
- transaction
- a2678b5fed9a2bc91148bf4f7dfda3afb3357bc239dbb85af18a7ddba355ada5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37421
the chainentry 37421
- sealed to the entry before
- feacdfe6ff2c5fa860d8ccb7cad3b0758782908bebc5248d63f8920394711073
- this leaf
- a69f7f0b689221885705e466af86cccfdac7950d175e0689e101b03ce34b409e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XvDNTmyfcM/To/oimBcqRv3txdEZJGfFth+y8gnYlblhZnY55JrSISmDqxK9ZDxYYe793C/N3hbLLmn9rRS4BQ==