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
- 11768b88456ef32a410efe7be2d5c33c74576c1df2be64f0ddb5e8ae72f67e09
- request
- ed970e3c8129309db3be45889c152e732b442c0f6833ab8c172d1877e58dc9d5
- transaction
- f7688c44cfaff7c4e6902300ecf0819b6afe185471f16ed3589b13253241cb72computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46582
the chainentry 46582
- sealed to the entry before
- 02d68b991071c2e48278eb7fd5dda54d4e36fb5d8fd903f37331e5d3fd5cf442
- this leaf
- 0275f7dbdaf3fefe1598c915b5635311f92343d847471989b05f47e0f30d8dba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ovwr4HUVQ2VKiInee5+ZYd62oxoi6KSyDJj9llf+cbGLb9qz4JxKsYHbKaQu6hkCGyLfn3jmS6I8AzDsn0huAw==