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
- 241d21be50f57406ab19adb18d05578230368bf7b081911c219d8421764a7a25
- request
- 7b1088d43cb5606b98fb519c76c28647a1a79250c10774b4b378d89983dc87b4
- transaction
- b6062dfd5121ea86e4e0bcd58ba31c6b83ebf61ebd6987761e43bfcf1bfe1e5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75740
the chainentry 75740
- sealed to the entry before
- 683172f059fccc7fb64badd59337ee110c1bc4d1c4a5e6cf00a3b4ad4bf03b71
- this leaf
- 98154370d10f4fbe332150954c770c8e938ac11353155f5bbc0fb9c7308cdde5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- st++aM1K8iAek72w/6R2gD1Y16uDyBVj3FDAXjsa16iVNLT6sVCnMPThSLMYnDqEyCvtUw4zTiKrA71I4ma0Cg==