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
- ca4946e8110bc57b5a3b7a37556ae37a5e9998af575318291cc3b09c01ecacdb
- request
- 7dfdcb717774dee9943f03260158be21c7de04d24bb0c805caa2c9d9c724d90c
- transaction
- 4ecbab2c57b3a185e31a3ddfc9d868abc31d4fa510bad230178933f6f2400a46computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49315
the chainentry 49315
- sealed to the entry before
- 0866391718c82473b9857ae154192490c074ccde36ca2b944384d390eb266452
- this leaf
- 1f9e4990c17167f23703dd768d01855f47e9690ca1ca850db124d42f1bfa2f8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5k7bMSodHKgsn5iDoonV8s320+uEOE7OKDt0C1JrcTnyDE9eqLfQLsOIvbn12T3TylO0VIAvzZZxAftm3hLmAA==