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
- 279f15c09305c0f66969505cd5d6b93c1a05225812d2c63906187535062cf1c2
- request
- 1c08360347bc643f0213dee86300fafb770f7f332bdcf482a7575176f644f0f0
- transaction
- 3fca4aab7c8e0bb644d230867d778a26892c46527a46d026fe13d13bbab1c90ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26475
the chainentry 26475
- sealed to the entry before
- 6f28c07b17fca0ee5ea2400fe9fcf3f34ef7fbf0163a8e5c068c5c0f4fae93f6
- this leaf
- 4dff14845ddfeb869dd90642923cb3b14b275f64124881205406a43fdf49a358
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fvu+MCQ6pEP5qZPG0pBlQAKdW83KSYaRfRDlAnjWRyO1VL8dA0TQPzLSuN5HMytMakE4nmNrMVF9RF4EyTGPBw==