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
- 602a55671c7a1de0d1036f8ba13d6da1dc08f1e417e4d97487ea527ab300a5f3
- request
- f951d7487253ee45839108144e6b211af88574a3f522d195a4e1be91fd69e206
- transaction
- 74a87ec8d7974bddf8221cb231031d5af584e83d90719840612b184d1df8a5c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49555
the chainentry 49555
- sealed to the entry before
- 34dc9c56a93c311013af5767371ee830423eeb52fed8caea8a30f6ac63b59dc9
- this leaf
- 34d91c9596dcb67e1e725314ecded0f0b9e28c86701fe21e5bc8c110db36b393
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4I6vNFyM26xINiAKuoLnByrft4Y297SfFCqtoOrUyv4KKIoLnWai1P7EhWRQ7dKTijC9wHZQMAUUe4s+RCC+BA==