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
- bcff8213bf769595d7461e96e33643ed4c2dae256ee314b920a1b37cf79c1a84
- request
- 48f6927b02cc8b97cd7182e8ca29a287e2d15c9dd10b5ae3834115b930e35c94
- transaction
- 8e2d06a506512a3b6c373d1e986f9ea8faff224891398dc8210c566e2950c62ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64045
the chainentry 64045
- sealed to the entry before
- dc753163d13dbb5afa8f5e7979a07bad345cf743d3af6c2c174e78aaf05518bf
- this leaf
- 807c6c585d6632fe13668a0e962401f992a40cf5cf5dc31fa6c98d48c0160e6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oETfsSOrHmGHbl51u10QS9/qdVwB7sHmTvc2p3D5BWqL7FgyzoC6QfiqSs1o1XTj2rI1T4iVWSxtlAjJSHmDBQ==