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
- 3746e690887a3225ce7a1c89e51a0479fbcd795bcebcfbcd85d3f662258cbc17
- request
- 61d8d7edb114eeffc7d744fa78ab3795336424cea70c52c856dc8fbbea0d2f36
- transaction
- 60306efe52e16d571afb65f9dbd6bf1d0d43bafccdd4dd45f2d06d60cc51ea2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39136
the chainentry 39136
- sealed to the entry before
- fdecd6d4100a7112a19127e604082561fb9ca6cb4846f835a9ff5e6fdf1069e0
- this leaf
- b772378acdf3cf623891548b2536a4ce4389a22be510543bd8bee8acf809789b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hRCmhcq5ZMP+y6QprS1OPBBXtyr9AgG9+K+vlpqlogQyX29jmMB8CJR9ZCKDCQVqKoWx4Xvgb+D2MLfad71uAA==