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
- 403f39449be1e14a8d548e636e6c95228ad567e447ffe393c5fe18c12abb3e50
- request
- 7a6af7cddc2df998d77f22e3addb635686bfb516b1e65a1da2814a9d3fb6676c
- transaction
- ffc8317def37b33cf6721dfb6ee6a0aa594b9c8c7da0938fa03d2f0e4a1948b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11757
the chainentry 11757
- sealed to the entry before
- 4861ec49e8d295445645bca38aa191b955683b1c26d39964c9ddbd8138dc3899
- this leaf
- b60797ebef6e0d868738bad9af6dd85f8d6efbef481813a950fd35b925e8d6e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /f5BFGTrCQ1ZygRLC+FdotebfZmA982LLCKz2QJzf4wAZTtudZ0PKE77rXoV88hWMuqE64/dJY8eMF4lWLZdCw==