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
- 207a817cc8b63675c65d4dce812c84bf0010bcddb5101d9fa69be12bb5a83c9e
- request
- daa5a6af1d14333bfb773f8926319342b5ea739123d14d03297614b18450ec74
- transaction
- e46e1d22890465f2700dd32b8f9c2df06bfc88ba82357c5857621ec4a0252d74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3719
the chainentry 3719
- sealed to the entry before
- aec9148c2c7b8cb012d7c912997c2be2491546ac114b43f0b9cb33bf20cf03ac
- this leaf
- 193673d2174cbe8beb2f011ced0be6dec1efe3961a14c51f8f7f07bacffa0ec0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c3WITLOz2HjyKb8IAVD+AYg0DL8EuCC31vG36525a51ploWrmdILx4e2jkWCj1G6FRfcZrD36k3XAJ57gDbyDA==