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
- 88e9a14162847339e247308d7181104ae648e95edb6e59b3113a66e569258934
- request
- f3842d6d104a2403cabb5a3c4d076bb3b6a6f3d0636722cfaac5915b3467ce9b
- transaction
- a30953c5536c0f87f9d37c85fc51957077c671015016107aaf32b277c132e328computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16058
the chainentry 16058
- sealed to the entry before
- 8a62af44942f2a6bb796421fd4123e3d39da253f3212b3d765c3206bd3b874df
- this leaf
- 752cb7401a2f1b61cc1aa27256d2065190aa78e105f644fb12aaa8478725e3b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2N4EQ9xRR7iz8nUxKF6pmtBLbwOAGAfx0Og4+AJnxNA6Q5QdX4nNy0pfSq9YDt5JPGnaY47Khauvf9m8Oi9ACQ==