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
- 9bece396c6e2c0d415f352eec52bdcd1ca199b60d2e46a3ec8636caf6f63fb5f
- request
- 2839a5500e8bce274a06d43e41d7a96ee0e3abfdfc2ef46143b1532524e3b884
- transaction
- ef41c7cce375ef9a735f9c93f74ca0270cf2e7fab5afd284f52603bc49a04e5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 476
the chainentry 476
- sealed to the entry before
- df4fa6496a5c85b36010633a79c0fcef7fdd9514f49cb4cf506a906f0fb41530
- this leaf
- a68cc52b38b0bff1a37070296d4e757746373b724c6d9f5e5b224b59f5ca66e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f3KdI7+xGO4JoA8Temza9YUON9kJuu9tVXpTLnPAe6oSzTSxBd5h8weQ289J/Oi5tQkitEeV5DXwPIIIEBDQDg==