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
- c69e4a2faedefcff51610fbdef5c03134041493840b1e39482a5c69745c79e49
- request
- db068a69edb620aef66b9921425864ef44affae883cb3c63979c557d00ce6175
- transaction
- 468d150ae00294aa9874b372074fa7843f3ed8c3f2ff92ac677ea43257c9a1d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 806
the chainentry 806
- sealed to the entry before
- c92ead1efd5345d2ce26251904316f36f042456b4df2f93eae239759e8a5b2f2
- this leaf
- 5db6a90f2f8b5021912cd7fc920408954fe0e4a21b5f715b3292232db172e530
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zAqi+d6TrV3BfiQJTZz2LI1k1HQZ6GkmFwPkKkwnQtiAWfdbfVt3EHtKk8aR8B3zvBkUi530vEm4gkx1V8GaDg==