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
- af0d7f0243af830789e9b1da1b70a84adf510c7bec2effde248beb43b90a9aaf
- request
- 693f470cc8850ebc3d9797a586e23b793b6de6d13fbc82752aaffd4b2745b069
- transaction
- e7e3192577566d2f57dc9a65af0ac79bfdfeed7b6ae37ab73804c56b43ad2b61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 391
the chainentry 391
- sealed to the entry before
- 456a2276f2aa06e79c5f2cb054749a6d46b4846269faacd87c5761d3766293ea
- this leaf
- cde608ab900de293ea2ad4e9e4149bec23ab3c7b568b77e2f788d11e65b6e47b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- akW7n+UB/XRm5r9xS2FOOpjukJXy57kZ03GXqx9KH+iMBsRTTqNXxQShDKRa9H7NoFsfUy7oECBjT7DjmuDqAw==