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
- eef93eddc36ef050ce05a19d6a08bf270c3a7f0d36778fb1c1b618b0c2c98df9
- request
- 8f24c516f49e53d87167293cf2f00e1cc99b6e1fd10062d8a62012bb6b18ba01
- transaction
- 4d5b560ae44b4264315a072015585da249ffb3cb2f92947c2e50b0028d5a8b61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30018
the chainentry 30018
- sealed to the entry before
- 3c892f8f102a4b329c6ed146e810b1f93d4d3abd7da702a05da235cfb92cd758
- this leaf
- 8fd2ee64194e155808df9003d59823b602e5e0d2bafb3a2bd8b7508ab339a798
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7WjGvjbJgqmFnxCxRaQZdN7PshJkgLx279+G5b0d0vdQxAn2uuTS07FJd2+TOE4Ki7jS4+9DyhUYgFD5+xZSBQ==