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
- 80a002af01a87f59c252e6121055924ad773c192243e3004e04b90c1b3a1bb60
- request
- 5bb91e09e59f4fcf5dc4810dd873c81b5dca12948b22b4700876408631120d2f
- transaction
- 3f88c437cbda59e6b79eec276fee9db8e5c2ec5a0a6c4cbb13c1037004921405computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28555
the chainentry 28555
- sealed to the entry before
- a7309d0014d6503b5e65da3a745832d144217f5ef1353452dd2ec36629141e15
- this leaf
- 796e6a403d97067dfc0fca3b74fca20d0baf89c9da9aafab9f30832d34f8f080
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cMPgiAbSVRXDKnA2pNFVkxY2S8KTI1eTMzTbAMjcVE1z7sQ/kqvKyYtQBYSyWgMLmpcX3pym7AhOY2qIbdICBw==