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
- 59ed9ad6f8a5be9d71a665a32f543c37bc09fc703c87a3ed5e66de4038da709b
- request
- 119dbfc400cc2bb4fce903c96182d4ffd7f67047c0cd6e606d3e08bf23d38563
- transaction
- 95ed2652a11ce3a28463dec5c0cb04694a8870397501a50a7d38fe53998e7e88computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 411
the chainentry 411
- sealed to the entry before
- a78b30cf16d3162f8196a6ac72d3b347f613ca7423a505cf147990bf07ec1d6d
- this leaf
- 159c55256a5542358be506161531a5908d19f62166e3a94e122f26a094065817
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vrLDVYbFtW8Faa4Mm5HbKHcW0ZJ+t70SziUbngzlMXXdEpCD4qpbzcLhiGGNrIgqvVgODpRQLMRcuJtdXKg/Aw==