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
- 7c5fb61938b91e5d660f6d347a4ed1c4f0917f15682dbd06136dacf8dba54729
- request
- b74357c22fb6488fdbc63c0527df953592713e68797473a97ba9dee25fd1d625
- transaction
- 7df41f490583050c140e8ee3afa1cb33b2d4707ccd5f5a4df240e53cdb9a18d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9112
the chainentry 9112
- sealed to the entry before
- 58d0f25bc213ab242e80f84eff3252d24c331049690a97982e326b37a7561cfc
- this leaf
- c714d9460fee6a7e02a9a38cda5150c9b71ac78b918e33dcdc519613a6f4cb1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oOajqxzXvddzqlDJgnoQKs07TJTcQB3BFy/YYlSdlOqxiotbZ8wfd4TScw/ZUnuyR6gX7wJV+KCAr8sa6+5jBw==