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
- e9827bccc5bef8b07cf07a23c3ac34241cfa11bfe26e77ecf81cb74ce9d5969f
- request
- 78372d91c39e6da06074fbf4769c720e8474bf1ef0e5daacd8a3d7eb98f6c961
- transaction
- 8bda657cd33be8f64b7a7a1e271d54076b6ef92bfbacc81860dd3824a4c2f5c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69944
the chainentry 69944
- sealed to the entry before
- a503cc14d417cb49983845fb23c517a247bfc5ef30fcae89f5332ea2ae4bea1a
- this leaf
- f8f5dbbd417963da0b4d82b54ae9d374ddb5156b007550d43d52bb14c54c410b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Wf2KxMbErvKkibuWP9KMTvwxDaO3NR4FcRHEEYEIJ0iSs6Ip4waNjE/qlyskn39RJrA6/HonNqKKjVxj+a/2BA==