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
- 314deb86a9f74f011b93d9660935e8eebc1eaf22cc3645c2e11520f6b28883a0
- request
- 46f72d6dc27a132dfcd81026c912f55a5804b7b63ddbf0568f3bb16e39b4234e
- transaction
- 13468a1a274444a39e093927d6fffbfb11d9427f1db17ce4d764f9cbb9b13d80computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4276
the chainentry 4276
- sealed to the entry before
- a7a21eb91d7acd3d4e98bb11d05a6c3cefbf8443170aa366a60c82ef8ba7d26e
- this leaf
- e896e3437f7f94d6918221afe7c6dbcc584f98d216d57ade46d1fa983dc2f0c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2mnmEP4rHAW7BWVB8D+mLu8SAGsSryJJ4LsKKoQPEA3sETLP7nAJQXwp9O+eBku39VYN5NYQ2QGwWu/vvXZDAQ==