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
- abbd956f970fa30bb2b11044d9e57bcd90be697ef0465706c1a6f69ffc799bb6
- request
- 584e6758c866945848a8b91cd52b19d2d8d36817766376ebcc61e1e2ef3bbaed
- transaction
- f7880cd04893e05dc0467b042c045b5877bbf7695d53ad29eb2f5877febd2b73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39023
the chainentry 39023
- sealed to the entry before
- 50b372fe3ffff84db98aeb7d36d5104a67096f00ae3a5d25ae51886f6e5d4b45
- this leaf
- a29335fd42859f7edc7af03b75de574110f61e66152cf2cc0452c85ce65ee591
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ubS+7o6apCYj+Gel+aYiRgwNHVbRrpMXjhkgO7rt87DKQlw8i9SQMemYeNjSstukkZmr+bURlx5eOy230UTkBg==