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
- 6bb13f07d9118ff87f9389489980589b14708abbcfc43def6bb466fc5cec46ea
- request
- 95879aab9729098c3ff3ddb5e53df293d7f96ddcc3079067a21f3f5d9eb8e8d4
- transaction
- 4e0fee22cb4f35d2f10a83459a13e1944b1391674764cdd0e983b853bd897a2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42418
the chainentry 42418
- sealed to the entry before
- cc91cc68866b45bea813f20474b671e22b8698ce4a47ffb5eb61e6a5f34fa280
- this leaf
- 5a4d8f86fc61b9919972a20c843ee3d80ba490c36a84bd6b70d1c4b8fe0319c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yub/K6Etmrl/FW8TK3rFXaAjjJShWKijyS7/JFUP+G4ZD3fmMK0FLAGSnAXNE2WP8ZBZBOKvS7tUmLXjK5iZCA==