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
- 1f22388a9fbd73bb71039f80b8962f4469d6e4b712904d4fa0b7123e73aee6ac
- request
- 7d801fc5f1b23bffda20d4e1eacb5953202e20ad1795393212dc5b06ac2377a6
- transaction
- 3701a2872570fa64b5a63293ffe1975faa94589be44718d986f516ec8fb06ebacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49961
the chainentry 49961
- sealed to the entry before
- 96f2d63efbcaf8ec1642b8075303d3c2a525591f1fadc6868840be58eae46924
- this leaf
- d9de0f727e5561d6272f3efd6b635b57421df4e3eddfbf3a58fd1025043a9559
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S7EJ6758qXaPG6KlZXvKIN3X5+QqLjixOG3knKV/Lh3L2NtmZLmYbLCfjE8dJCvNkHBtpdp8vytaEeruHQBYBg==