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
- 6b67def2a245a9d03929c97cd81a52aa52d0423adf11c117aa90a050e0f9ded7
- request
- f6f7d3fec01d9b17444a7f2a89382ebe1ffeeeba2089fdc83886e467c4cf96bf
- transaction
- 3c0e63b992b0fcd3422c0595527de4d83fcc5f6a3e71a9e954f5b9925197889dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49324
the chainentry 49324
- sealed to the entry before
- 5953d8be566dd3eb208f38692c40978b7487ca5f39e3cb4b0b92ec54f2a01a58
- this leaf
- 772f70ca7e9fc0cb832c27a9954ad684d5d03fb2685f7111682be2908c870887
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2UJofkwMdDI2aSwmrsfv0WZI+iR3M9ACCk52d8p/pfc2FRa8R7Zvirddos8MgT3vXrTX1com1V6E5ng2/KIcCw==