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
- ec3eec8b4c489ddc7379cebe032b44efdff7513cefba43955e2004f7062f9472
- request
- 3c5ab1b985c8b4157f326fdbe0b77119c49de0d020803f5e0e455796ec3e2d8a
- transaction
- 325fd88695dd28b552ba55e690ee245edb96b79d4ea5968a3546ea08af343829computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40068
the chainentry 40068
- sealed to the entry before
- ad579cc2b625b7d660fd501fc795f9f073cafac43060007b3372e63132a7f65a
- this leaf
- 11dcc263c468f3907353fa48bb7357c716d9da74702406797da5f0c104edc38a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BkRcIGAGHSUtl5bGZNBEdTDFVCQ523h60WQadLt5fZ2F7Ond58QAmggsRE0fHocd2vPMaCeVo0S6AkRmHFB9Dg==