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
- 47e64e181613d895f9985ff4dc3bcf5e8b0e345ddbed68daef5ec7d369c95d78
- request
- e1c8ab88a264c0b718c2755186f2c142e5ac3aa672875749aee04eb9fe484495
- transaction
- 453a9f4fab71e5d6d3c124326afcfe297c1b684f614a49cd881b1afcfdfa520ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29391
the chainentry 29391
- sealed to the entry before
- 8c4688b0064e6175750ab2e94f8112d4601c38916b39e2bd772e88041e5ecb8a
- this leaf
- 12288493d2cf9bafd94875c96b8e69cfe06c39384a0dce8a0571e217cc3cdee7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 22Xq/GNmSHalTQ4TS9efQkDzo1EnXbmzIt0kZXUBp634idgCvLjfLuRLIm2PmcdPTJX1h0UNHSW5g+PM4ZnvDg==