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
- 9bdcf9502b773b301196f16ec139893498b99dc36b859fd0c36c24eaba3de747
- request
- 201af25aba706ca66c42549d2e1e56846197585574c621de392823acdf376682
- transaction
- 162a859d0a6ce1bd8c75895a6ccbff8af29020661254beba07eba9112c535765computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70382
the chainentry 70382
- sealed to the entry before
- 6f6fc9f25b83e41923b5dfda3c305a19b38470c11d54018ba62761beadf6e6ff
- this leaf
- b4df506b89dc8991246dc23f86c5a2ae8bad31353d9704e74fcdddd75cde2128
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cCCSR2Lrbm3adgcGXgiNYd9Gi28c8fiZlsJMM1DXmmnbe0QGvB3LFfM2alIsE2e7i6/H9/CM/PnEtZLSe3KcDA==