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
- 6f958bcdb7e2f6468310c289cdccab5731808302073324b60f83eca4d3b274ae
- request
- ee8861850e4d9d57a1f81780842c45911ac26204f26fe43dcd494ff997e882eb
- transaction
- d600d28aaa9cb87744b6e3d2cbc76662430d71f914d37fa1e9c30a06964ebec7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51319
the chainentry 51319
- sealed to the entry before
- aaca1d46e3b41f9cfcdbaf9bca008d445b18b1d17e0df27513e61f49894eed52
- this leaf
- aaac7fba4ba26e566845521ecc9fc4e2b5e169ce305ba5f185044255ccf4080b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AiZIpBRP+lyqGUhX6YezhmVDzfZoXQWY8UIDVJlRuct8stfxo97dPsbjH5SYR6wUNdkW9+0BZbF8Ajm/NaKrAw==