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
- 00c6c04d76f26cbc9a1e160409421799f84c7ad2170685a70c9ba387856a5642
- request
- 0734dc812a2046ade590a1e39f98a23a62fd2ff748ca1703ef7b65396236513b
- transaction
- 3c1c95b84d3af651696d5471c2943cea2e19b0b18a9b38f04d5e03ca11191fb8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62461
the chainentry 62461
- sealed to the entry before
- e7627410fe83f0a8b3b988357dbdc0d29d8910bb2c22fb6b06ebea036eb717f5
- this leaf
- bcdf51372a6af2782d3a6eba7f774e57d4abcb876f86c79d9cb618d9ce09270f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aH2vRahlxh6PO6cW/PaWJEFo7VgLM2oPgkBQ8I6wv1ZsXZwqdMWJzocdfAVR9Mqn0XVH5+rtm7jtfpwc4LO0DQ==