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
- c4d80b6307612a203f0cfe3f86a4216099ed5debbe3b51e97ae44a225e13d10f
- request
- 541c87c1f23bcbb7290632d227073500f8a17b164d938ca75feb81704588c35a
- transaction
- e771e292331932d7ff440e728c63ee8871c30f74985f53e93d19d5752e683c99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44594
the chainentry 44594
- sealed to the entry before
- e17fdba2c603ba2a5b40b6f54457e3705351a00e24d754cb62ac356b6421d743
- this leaf
- d50d9902e79c8dcc47de3b85a93e02190f9aaf004459a2710bf14301fb6fc283
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZiuhUxirq8E/U9gFSVq0Qo3Jut+P7uZSypUpybpprG6KlTSta0A8DH/s9d39r8iJXTQnGP4ENmjNxnxJgOrzCA==