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
- c2968bbb994b9add2df18bc45fcdd82758f0003ca2ad1f63f4384d04595b912f
- request
- d66af116e1eee346133979992b0b7efa21e321fcf3165f6e7ea0a09bab280d81
- transaction
- 1eabeb4bc3bed3fd165f4819599d3f57cbbf67cd9342693ed4d987edee8c136ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72481
the chainentry 72481
- sealed to the entry before
- 311c458b94463f390a48e8ac9239f02d9e2dd74554f59c22cbdf91dfb24830d0
- this leaf
- de4ead4a59ae130c86c354d1df9d6bd63d8f8d56e1312dd70f59e5f496ace480
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tpEQw416mQIXY7GwE1DJJ0u0wXEivdUMNO18Cbvb/jbBmHsT4/EMirOlLSv7p9JbRnLBSmTvWvr0a7GVhnlAAQ==