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
- b4e99e425274505989e69708631e9bb7fdab3eb1d9c470add59a5f7c327641dc
- request
- 59bac26f1083c90d45077b5a5b906a0fd6a8350cfa85868f7fa049d86def9dfe
- transaction
- cb7dcabfedf79472b5f96636e59563ebd4fc0db45682887b4a8758b1ae51f992computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46493
the chainentry 46493
- sealed to the entry before
- 5adf29b8ba994ca628437e2c0736066941b3f61b99039892c0901b4fee7e775a
- this leaf
- 74bde4853c751bd1ac62fcc16cfb10f5d1277842b49f1e2ffb3fa799172ac768
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CuO90TGsKXNTtTZ9HZXUJBm/ye7ZIwg59UNnUp1Mqxx5RmIh8G09OwtjjMpXtCZIUslYOe5Ck7haFoU0NzjYBg==