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
- 7e6c78acb3db5e51fe8669e063a95e91a0f39d7e99a14bd98f15b3375734d7d7
- request
- e14e6a81f701e4692a57324087159c83c65cf1dee21991e5b550dc23589bc991
- transaction
- 20bbf4eb55f679fc015d72a6638f59b794e1863a38a603b8ee8980fe7246c82acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63093
the chainentry 63093
- sealed to the entry before
- 06f2ebd17e23527d6e5077ccfa80e272ae4ca4abaeb7b91ecc33b6899eb5c71b
- this leaf
- 5c00b879fc16f2235035cb850094b57119be18c75acbfc6341df1bbf9ce9fe26
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WXYQnzDJNFQKDCv4LLTZt8oNH81zFZm9iXtttclmWx7jQGuQxU/ZtcZNOythhAhA/EXJpOKbrzOs4W07p15eCg==