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
- b315fcd6957d86d75f7bd9be4fbb20a2526b8ded36275c198636b370abfbc836
- request
- 18dcf5c722a3be3d1a27869eb5a42c652bbab1738d6a64f75583e5c285579584
- transaction
- f032fda4cd03fb34d565c2c6e656d89b29daf60b097c41c3356f9ac76f2dcf41computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75540
the chainentry 75540
- sealed to the entry before
- ed428d263c37ae6914c16a8f9ba2ea69e743a4976fdb5d142ec70979be2822dc
- this leaf
- 263887b9afb7b30becfdb06d0207d8a5d8bbcffe7917637784e102d0293e0d31
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BoIM498GSAvLbA5pfwYxCTMyak1A7XJDYaaZnVbHG6drMZ52W1AFh8D22cJ5+FLNyYT2vMQUYVo7Pphy0A7qDA==