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
- 4671d3887d04885fd08d1249ffa3f46afc1d56fa086caaecaeb8d8796855aea5
- request
- f13961634f29b38dfd1aa630fc019719c11a39432646b1453fbad04a24462952
- transaction
- f6334e520043756e9506aa648c93514a6f2f9ad01bb061e41a7a7b7d83e16c58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47018
the chainentry 47018
- sealed to the entry before
- 9884bfcffddd58e2a0f767a5e44efccecccc63bd968b864cba3dfdf4a166fbe1
- this leaf
- a69c9725a515a85f585d14ab3befdad04a3a4e3ac4d5a440e97eafc9c52ae121
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LtvHgV65N4ngCkf0SgrRI8E2OBvzuuBKl2rtGg1IQ94sS6m2o4eBtS+G+lNUEim8JzQ8H5M2Z1lYIDemB5PsDQ==