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
- 5c7774dca6ba191b25fe8a31751c468d1567a0c802886a944a76c508fff6e4fd
- request
- 705a7061298fe723a670d58ec5bb7bd19567a2f0438931561e55524d076e891c
- transaction
- 9df871f9ec58d5fc34a8a7126d643fcadc4c221513533a08240fe39f50c1b430computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51304
the chainentry 51304
- sealed to the entry before
- b1d7dddba1c94c9cdfcf67bac7cb36095bb7e10ffa5764431334e171beb20d02
- this leaf
- d66e0f215daeb8a8518ebafb8ef43e1a4fa05a0b12b0dc8aa5262f0e7dd87cf3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5B6qVp3L2Cfvd01iW661Q0Bus0ggymnb+q48SMYtLk9PoZ3e9uBEDQT9t29bZs2+8DzmyWHz/7jAeQ8xr6K1Ag==