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
- 1ddc659b1441f9a09d080fc8d220abd90eb02fd45c76332a9b0326dfb74fdf7a
- request
- fe5bb56c91efe73012dde2476425488d486c8d9913173d586666b9ea127435ad
- transaction
- 2bd1d30a26532a033eea0e12d6df077eb1dd729929bea3f19f05a24e473160ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69467
the chainentry 69467
- sealed to the entry before
- e6ac23da4bfbf7d57136249c8b5b38172878525bcce6ee22a1acac79a94d628b
- this leaf
- 6c75583cb1f909338c736a374cd70ec58a9d28b31d3fea548c4549ed5a7c720f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- btL91SBpdLbdlllXh5xgYU2Hliot0xhosw/SBV4SnDjAU2STMclcBnQ7hfXRW0vqxEOq7nlssZAau61r9JBrCg==