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
- 322312f49afd7b74d1579ce5cdee2a09064f3262247e4056cda42e953553663b
- request
- fd17ebdeb3a79005c89fe6708c957cb0f1736617223e0d43e585bcb611bc1260
- transaction
- b399046e83b737fa575a551738779016951b1df0bb510b25555fbcfa8b0e0731computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28108
the chainentry 28108
- sealed to the entry before
- fc748213880d498212fe3b02c159c52a91277e7d4070dd879b6c0439ebdd6ac0
- this leaf
- 509e8b4dce1a8c0b14c3c4588c8f4d2fb8475531b0e47b510d5791c402dfe110
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z4wuhXFeEh9sr3TVIdf/F/ER3ODbBK9VZPrvP1Yy6wGLWZxwW72ZQeFVB5bXIyYHRDvfC5zNFyhuHJlURXbAAQ==