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
- b8eb16a4facf21e9f1a14d01481d351b8843e9d179c88515304ced6e1d9b2505
- request
- 548ac5f260e00ab7ce2ecaa64d342cbe46fe6cf4e7e061695c74df6ddfdd6d82
- transaction
- f48c760a1aa3a1ab1afd0e858c4ef106eed7c5d5319aab0198a1bd3d45198571computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60558
the chainentry 60558
- sealed to the entry before
- 57393d65e64f1065aa9c860708015cf1ac719cb9e0d5228217c2ff4d027d535f
- this leaf
- 8f5731111cde080891104f635f0b4e0c83ba546c0c5f29dd2aa4437b96a468a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V5wIu3m4vEX7xGsJ2JZ/vQOCZY+/K0T5CN///xbyR1dgWWa/9hcaJc0VZMSoTc6UddVLv07tCY8+gtiy7InZDw==