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
- 43b9fa5f19691fceca967f58d3d653c1a20cb691427b1ce580b400a340f5a7b4
- request
- 600f3b93877213e83eeaa2b8bed55a0f987fddfb93d1d643b793dbe19e7ebc5e
- transaction
- 442f83b4d29b818a8a6b2c50818101d38a2509f72a8b29adcc6859e105a26e57computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5356
the chainentry 5356
- sealed to the entry before
- 23c01d8d83efcd38de30d434604660d3649125554fc5a7bbc78e2098f8d158cf
- this leaf
- 3cbff5e9891d7ef925ccb50aedd9bb98d855274c7fb2423b43d18a5ab49af0e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d4lo8YcKCaTQJSr0HRTSV3B473X7qeDqQIdOUMy1nJGqk91aEMsCUCT6bl4/+lggY4VlT5tPg81+Ce7p0RpeDQ==