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
- dab4580fc64af595c5f349175c6c7463923e81450f90d001d572c88ad421613f
- request
- df4be54f30e6061626c01da56b3e0a57b3394b36e453e04aef88017f55c03c57
- transaction
- 70df901a53083749ed4a71381bc95bd744ae83959514b5842d5a2f6e459c1670computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77830
the chainentry 77830
- sealed to the entry before
- 576376f74671079d686a53bff048eb7abae6f24239a11549d68e5d3ebab528b9
- this leaf
- 010e04fa52256040450c0258e1e36c1f93dc0f3434e6720d50938a8b23ae07ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SoCOCtUYt5XclOYBOZK9KAZskStHjftacjAQF0upwdc8o3we0uyzK3cqpXVIpuQhdmRrvlH+/Isie05Mk4zzCA==