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
- dd96e9dd61f7c0203588954ced29e8f91c2977be6e31c74d9c162c16b77d075f
- request
- 0175ba8ed97589ed7a3e62034bdc181c0eff0caae5d20fb740839fb9813bbbfa
- transaction
- 6e560c38de9f421d6df2c59ee895c15c2001e62623404d5d3e7d730d93a1e1b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6515
the chainentry 6515
- sealed to the entry before
- 192c6c2a1b7c0daeff26a13bdf8f2d922cd68c594ab230a0f3d9ed10e9194f6b
- this leaf
- 17d01e2594a3355ee18f089d3d69d74b8346b2e72a31a6cca6d37e288799d362
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8XgNsW6dAaqrKeCWSuf9ihkmYPuhLLrXcthFsKoiZjc4neoWVoKOFwKZAbR8BZ+vTL7ZocVF5fuQMK6zw3cKDQ==