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
- d0bacc3631c2e3ac754434adf0196edae41e7eb540f74c9c3b2f4dc1cfb2af1c
- request
- c5accc26b1a6f36189d395ebebf111417ed31712dec8e98d589ace5103e41e76
- transaction
- 720dbc52fdd6a88b4aa9e2986d7c7f99db2e2a1f74950f4df210f56ef02f4cc5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2090
the chainentry 2090
- sealed to the entry before
- 76e45547754047002544a0d5833974e790b22195e5acfbed11165e85bfb89ba1
- this leaf
- b1d5afa71a9f65b8b2185bb462ada04223c9121c1a4706782dda2d9178fc3a2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- glc8XkZDKGebiPMxDnxicnFpKAFhQlwhpEL4a6CaYtAxpEUWqz1tcpy3PlYyhygMRk/ZENt16udTDzgcUAZiBA==