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
- 4143854fc041cd08a8f782419f5fce58fbd6ed144df68d7f15f2e549334123e4
- request
- 964aa092322a3bfffe277257fb795e162c3904f8b94fcf82bf6a8ae69edf0caf
- transaction
- 42f42e5bb9eb4fbf5f40de5e0950c5ec54bd7ee32c901041b2717e89e0269319computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63314
the chainentry 63314
- sealed to the entry before
- 348df1285b806aede5d007e13e6cbdf552ec21acf465522f079e85e40ad38750
- this leaf
- 143d1ff11ba740b2cd8387633602af6fda6393fefc30233eb9440a5dc33fc3a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D6PaEBiuYEgNi4SY9V+YzHzWzmhmwvWcpsKHpwdwrZrpE0GNZAIGvrD6bzKuUAd53FdW0AnsXFTmrVaRUhaBAQ==