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
- f9e5bba6ecfb3cd16910aae08e6a576d7c807027bc29afa503e5bfc0e1730c3a
- request
- 9426c5cd47641c6267051ec0a7e3056b10059b3ba98a546b6341bb48f2c5003c
- transaction
- 9036d2a9ef52a6f87d30ad5f6a6e2cb4b73ba5ba8f19cebf1ecc70c8583c87b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72792
the chainentry 72792
- sealed to the entry before
- feb2b5731b874f435a4ea85b090d889cd0177837e5f55ecb3e66d6db6a111a20
- this leaf
- 4d9160483e0adc83f9e49f7868d59c3c3d79a7116f17beb53c47163597bb51ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HRJUDG9gTDvBPQaUInEM9n+3GgvwPCtdSzyU2/0USVkCpnaqMi9rCeVul8TIU0ziS1QSptTrcbKcM6rgjSSXAw==