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
- 81f5d5ce1c59f2a18a776cb97732302574a6480a7a4437e09ee3333c8fa2f9b0
- request
- 76cb0391d742a4ddef86f4ba6dc8197b880b86c30b068a8115cc57ed6f4b7a30
- transaction
- 3109c8034f513886f5cfd400160aa6683fa9d6d3ae55bda3b3c5e4d8aba8c9b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20431
the chainentry 20431
- sealed to the entry before
- b112143f9648b566edf1cd17df1300f0cefcf2741f3a3f6ff4e0bc824e649cd8
- this leaf
- 7953f79a91192317fdb1b7d7d9f3b92393e843351e6e6a872f77d933e381d718
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gZLzf/nmRAnZuG0i2cjakcKdGxbO9kIkDmVujk4b1AXcuBSZaNWLaHeO5mcNkMFoVSPSbefIuYrOFofuqgBgCw==