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
- 392c918d57b6412e3080599270a490e1275e331384aaa7591d4e3c6a7053d6f9
- request
- 87133a99dff420a27b02a74c6a4a4fbe08ca13994c5faa79cd685193d4806e8e
- transaction
- d796ebcdfcb424467313b8ad43e88db26ce281a07180aadb8c72a61aa96b4f33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59587
the chainentry 59587
- sealed to the entry before
- 6c634c20d77e44519acf7429ea5778896d6a3d663f590e7a4710b6d73d74b34e
- this leaf
- 23726714dcf142abe6fe6356428f5d50085d1f45693b9beb38bc6ed046c50a5a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rmcpPapwPeMIJIuXpB8T8p6mYgbYjsWT67XOd8WPilRhhewWXpaIJ1QgkhFfi9oJRcpKtMEkHTJx410hQWNUDQ==