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
- 8270588c2b97ba4875225acacdd3a98e09fd3d72a496f98a9c3d523369c40585
- request
- 54dc0df28dc351d643808a85c36348faebcf506bea0e9d55995015d9f23f9700
- transaction
- d9cfd9833e175776966baf1e0699926a075eaae5472df693cec7be0c39ae42d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20127
the chainentry 20127
- sealed to the entry before
- 8466880b7aaee80f135e584705039cafcd2aef6cf0bf6891b8ab847328899ac4
- this leaf
- f3f7aba95608275eaf024c2d6c225dc3e8ece70a6d4a89477fbe95e3d2efe619
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /38zBndHstlTHbiAVBsxQt72EgtnyKjwIQlGcAMuf3Oaloby6Unn5WKn1DnOSCECNESWEvEZDXhE0CT16phrBA==