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
- 2030a790cfb3c3145ea817923b8abe6327c6335f1b4c1906498c158038ba3ead
- request
- 3188d0970b192262915a5e513580386390979b4f37acd44c8892ee298a8e7bfd
- transaction
- 6672eb94706cd2e0d36975cef66aac3bb01f2f3c50542ccede7982daa85e7de5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10637
the chainentry 10637
- sealed to the entry before
- 032d98bce0425f42c60050d2220a8cac21281c15807ca3e009864e2096a0dc28
- this leaf
- 1643c1ce4078b689e53cee39e7ad0dcab294e1739d6524602baec9aa47eee063
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nj1aeqhMKSn6Bc3WxExq9BzU7C1DMk/AE0/befZwe7sDEYpX/U+pZ92PV66BDUdCVDjHvPlvBmpFmV1ksRwCBw==