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
- 8fb2c33bfe0bdde93ca4ca9c204718c3db5f67b1d1ac2964a9934a701fa8e892
- request
- cfc7fbc8d7436c3bf3df2fda4be4f9d44c231c4651769127e98dbe98831d2231
- transaction
- 5df2a08ecc06bf4c8e81f8c8dc9825e08ef9df5e4625d1401b2523be518cb650computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68018
the chainentry 68018
- sealed to the entry before
- 7cd2a6f135418106454c4705ce2da9e66cdcb8848cff99941027596cc4640e46
- this leaf
- c2069646b2a79c4c2f9a1ea7833b02610d335ef306ca44a3b5c23a1defec101f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2NFmGAlUKqnrWgiLEgbGEuE5BrriXXPlLqUllyBHc0jUdsE0Ue/HZsghEZHv/Po66qnyQw4W/7TLVKuXESNqAg==