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
- 9f4743ff8e572ebc11c740e10d6e58790c2592e388f321cc9a8aab931c4bde8a
- request
- c0567f0141d83bfd282b5978a6cf658905f3e127964dc77d9ffc870660ec8eec
- transaction
- a30eb4047864ebc71eb69d062e64ed3192e07301ee9d50369580afb2e73afa9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27199
the chainentry 27199
- sealed to the entry before
- 19df428f6cece4b458f3bff9dd42af08ff099cb81ccda5915aee140436cec96b
- this leaf
- 86e7a94068ef46a8f7f24b7e2de6ff879327f51856cf6c117f37cebc8a5dbb12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3+C7sY7Dyab1iPOnT1ULkdd5IZROhKV2NUFQiB7mYdWuP+dFfvKtVZzoVsZYRsmkXNihwIs+iUgZmu0uH9xjDg==