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
- 94bc7499166656cecc0c1b8671eab480b1f67d129bb2d24c5f2b9765a9d9e65a
- request
- b37a0cebd159dd31a362065c3bc12bf4583a04c84769efc581b51fb197f1c041
- transaction
- 7e4d71be72e9aa21dc219a077cada12f779ed627b18dc63bc3ae922d61f527bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40568
the chainentry 40568
- sealed to the entry before
- 4cc20f841e147d2579da71141f1ea1e8a38c16de29b03904e3a4fee300455f3f
- this leaf
- 72f6300200ad176334622d8a0714c88507b90e1c7debb1e70a03776fa639701e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 81kzkoujKPTaKLaYAUiH2UoSeSFqxJXARhZKP+cObWQKreFCfGWaFQmJPkVIhWLpnuCA6ZfNnljHcH+AqYLLAQ==