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
- 116c528132255d0f6a02cf6244636c97ebb3c685911362613e0b5a83f577ce39
- request
- 30a1525ba8befcfe1d9eec7e7f44fcd50aa914e81d5b24e32b2ff8a20132f6b3
- transaction
- 364f65336695c5c0d402965e4d469de38008ab563ce35e6eb9ea4bf9d2c57d8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65152
the chainentry 65152
- sealed to the entry before
- b04b17242eb960661e375d912572cbeb2d814e295935a432c25316878f029a61
- this leaf
- 4c4d08f40284af172e858c7a741003681e59c10e637ae7025053ccf65f8192ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bGuPtvLCeuZc5LtE4DXJDM9f3YxOfmG22+GKW3F7T4T8L3yA1I3H2pb4uyuuFo+HfjXY7RZ9/XSSJn906vKGCg==