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
- e9310b4bb753460acd16469d3f33db6bed06e689fb9d26def1984316daf34b17
- request
- 2e8066813d5e4f57a803750afdcde2cd36590f8881d60b0be8c1a2ec7b60f1ee
- transaction
- d6ed3cf1580ab079397d989560c7d09e7d6baaa68a5bc735910d4cd9bed9acd6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23892
the chainentry 23892
- sealed to the entry before
- d9872851ca00ba96f0d8c01103e74e4a40079a5c0ca81d2c904d828394a12704
- this leaf
- c1ca73b153b758c4f89eb8174c8fe1fae60d173756f285101bcc882e02649e85
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2GkafJdtU8iwOeN/jtO+Q52iYWXj4hASk71AA4MlVB7YkXT+JztqhvaYlmerTekDWmp1XyBieLnDFbjz97ovCA==