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
- 8a572be92e962a4127e2819bd2bbc3550d18d49704b3dd15958587774f8933cf
- request
- ead1d1e59e2add19cff188bbabd8704034100439028ec0fb83c9eefc9c2c5480
- transaction
- 4c550204befb12691e869d63c36e728cbfdbfb189c1673f86935de4a8ee73449computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2721
the chainentry 2721
- sealed to the entry before
- 41e30c1a0e216ff87ce5d6fc193ab53cf1d3517429bf07874e2dc69e7b32063d
- this leaf
- 9c1998fe6b7b0bcb7fe562c2716e7ece321da125fa7e5c0bab6ec55118120b84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X14VGf3Y6ZFkQ1ePJuZG1mxv79XiBO+H/HtdYVzKHJoLBML4QsZdEGjw8bxMNTpnbBJ0fRFilf/ADqACf27CBg==