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
- 0af9dfb59de357e9ccf604797bcf8bb6fcf8b593e138442408855229d7bb59c9
- request
- f7cf5bfc2cb8a25ebbe4a4d07634a12d6e3127cf5bc6ba26b7d98bfdce230cd6
- transaction
- f7f69f6c2883ca43ca553efbe6f21c8efd3983cf1b99bf2647142b4593c1443dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44283
the chainentry 44283
- sealed to the entry before
- 6aedeba0186cb3a3b207b0affb6c8b4f23dafad972334ca89b1906cc38c0a354
- this leaf
- 24ab4b5770398bf75b8f50d1598b19fdd19e13042a6a83897f56993c423d54b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WlGLOxGcIJUkJn7YBxPm1G+kYKk+Abx+iQvYZvqvjYRJ/Gza3ADNyz9zLoUFfJGmeUNEttHxfHUjLmHwWnPeAw==