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
- 2b9aae1bce8f6e414046a556bf6ab9da65890767382213a223fd8ae4a0917fb6
- request
- 24b5b7d644e045db6121eedc59105869c35a526c91d8092da0ecc1820cf57776
- transaction
- ef9f70774482a17a8b26cd4df31cf3e80364d18902c40ba5cdefcc9f25f874bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23071
the chainentry 23071
- sealed to the entry before
- 67ecc9d7b82bcefb83505574fc61bde2dead10c4cd9956876fc9e41b1a8c3be3
- this leaf
- 830d1eca0a97e91519df4b9294d61fa9b9ff79c314635b669bc8ff4e925dc512
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h9yEiFll6jhwbjEkVAX7hfMqP/Z5byab1CcEeNj3uCI/fiLp4RGsHrIqUO/11RM5BQ5yB9zEmBqO/83N5AlJDQ==