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
- 0da33a4eb71f4f076d4281fdbc7cc2229e95da2acafc527744eaf4a2360ef8e8
- request
- 8d1deed67d8095dd7773eecaaef3b2c7176bb3c96cd6e62f762004569a6e590a
- transaction
- 4694c6a05b6a44f520d16480ab1000da5a79a590f8f4efdf51b03adfd401eb71computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55474
the chainentry 55474
- sealed to the entry before
- 52756cec8899354973d5de984ded47526ebdafc9ecd511edaf9432bc1f34908d
- this leaf
- e2f9e0ae4f01e86af1dec9c3e9a0f5c7987e1df61bf1485683960664bdff601e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C8AjlN4eO+ovEP0HaQMqpALh8s6vLB0QUI5b7lEZKTCu0swVdtL2y//twfojsHETkwDdIdu9jpI8IZPvbgtdDw==