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
- c3599dba7535c0ff8698ebaf04debf07a769afb3ab8f4e9af479bb971fab424f
- request
- cd9cee2d8d0e77414eb37192789951a46ff7dbfab38d8571368b38d681bb56c6
- transaction
- 1872924125732382db1afc96151b0820693d32c8910fd4470b9e6a387e3b1717computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68358
the chainentry 68358
- sealed to the entry before
- f21990ceb7e7b2065b81b22991951546ae307a121cc4fbfd930ac28b8765d094
- this leaf
- a82d0e94f27c70c52b10a9cecc0347fbe82a862f30387eaa075c3aeb35cb00a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Aw6Ph4jp6I0M2jzdjMkoPkNQ1uyd5TuhYiX4nnSFpmAVjyWM5yIHiyQ0hTh+VL1RXmlP+KZfbBlVZAwW+4OBw==