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
- 1ea695e4a1a5aaf026b075024db67178ca7dcc87105a54d4775a76d400dd7758
- request
- 08d5adf0568783f0c6d61a4746fac5377915fab98152e253d065afdbcbb81eb7
- transaction
- 6c8026dd3b334e31dd99e80f0c84101b50603cc88d3875bc77511943db9f290ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65861
the chainentry 65861
- sealed to the entry before
- a36f873a7d2da2bc1b442f677dc8a88269b5511430a69b34c56b89e77537f146
- this leaf
- 08331a08ccca187218baa83ac164f3009badec919e14ed7d7bdfdbf277ad1e36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b6DDBJqGfNs4ionv9+ZSvYgcc208MvIqkKzebd845tSrcnHYHREqaF1MAzqUWdqiGmGWn0kZgzkItpayKWnlAw==