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
- e5a996c87b0dd24e7b116ba2e45960835fb3dd206de5b6e99785c8c4b769211d
- request
- d9ec8da7c9d7e57846773bda35fbd73e30c09185ecca0cac54d2474a139dbd00
- transaction
- ae903aad9ca30b24f3179e143b5dc927b2eb3d44483ef1b12675acddf40cf6c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5336
the chainentry 5336
- sealed to the entry before
- b3b9cac6e45dc1a3ba41bc80b471cda638bfc509379d2a115d9a5352de18672a
- this leaf
- 3bb5f50046ad98d559c5a302fc68b35f00de7e697424f8f6bbe27490c95a13dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Alx5VyuSHkLMAK2Ikg3sLlG/jCD+5YSElahmZWI1+Yc7e8jRWWmiIVyLY6YrzeCsVD64draAA3ZytISOh2TfDA==