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
- e6335cab8f3bbfaf70c109b603a572c26dad53187b5b9cdebc92869daf472627
- request
- b45feb68cb4014458cd4225bbd033f6258d5dd166ca662ac06f3481520e010c5
- transaction
- dfb4f1cdb6405a3224436893b441550411aef7cb43082d9b67e93a29fd465bfbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7071
the chainentry 7071
- sealed to the entry before
- 57e6274a6bac03525a4b46ad3fa7cf5c28d9cb317aebc26c6f2cda7bbee61354
- this leaf
- 3981724a9e049c213fe0883cca8214cfd41aeb22cac19254f12beeb3a23520c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Glbd9KT6UFnIy+K10W2jeCqILql1yPV0fs642R0vy8TTrrCtpSZId+PuURiUsSqm2vuuvUvScoVf3cV2OLczAw==