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
- 99a8d7c6b670097dec518e85e9e91a443623a4da7dc4f51dad8072385bc5ec50
- request
- 2b789253574176f969a2c74ffa69c0d369fe09875992408b82c8f2e2d2fc418c
- transaction
- b1c4208455c060dcb64072176c448760271ace9a50756f1d1784111d375e4aa9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68265
the chainentry 68265
- sealed to the entry before
- 778d9459fe26afa0c15a795e905866c9bfb683c605d4daa434692a6a753218fc
- this leaf
- 0e2cba19f9a49ff6fb48bfe9f2f9316300890691c9d69093ebe0aba202280f43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- unX2ZZQlU3BGoQiANZRtpbaVGxLwUglxARc9pXpOgyKufLASTWrbVbMoQnwyGOcObnSXQV2ZnRFLDqsrMBdaCg==