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
- d39742a06c54bfbde5624c51124a8e9e6904c331c2f99bd70ae628d379fbc6dd
- request
- 4f4505341e51201ea1e0e2e360acc163bd32676e752d88e9787cbe261bc67021
- transaction
- 4271c6127ac1380d5858e28c09d0c109b81c332bfc454f84f8be8bde07c6d528computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66746
the chainentry 66746
- sealed to the entry before
- f504b5e7d802ce93097a912fb91e996460f97b2b31d33a680498c8f1f7adaa18
- this leaf
- 0b25ccc648538dc5024bd2572f10fd99fc0e682c4929fae93e46a64da79fba39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ntc4Yao3b2MVDK6uTe6a+icjWbmA3FIVLp1Zh7SPWBgjrsGJH74zKikxwbs9IZl/dQGdPrPCZfn8FEzUtsxMBw==