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
- 872f37a963b15a5abb5ea906f87683b5815b6b4aea81e44dedcc9d101d58b677
- request
- 1cf9f464281368dc3f1e58a2c85179baecf9e64e6c48ef8218d489f55313cc50
- transaction
- 0fb2bfa3afda451fd12d8d3943259fdd340d962e32ebe24f0c6748c13728c9bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72373
the chainentry 72373
- sealed to the entry before
- 7e84edf712e97fa1034b4464c2fb9f3b2d1b3f5e66dfd99a51983ad6ce1c1501
- this leaf
- a5de1b6ce0ef6e9960ced691ff687dad89c4f94a373a96918be5568f77861acb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R9AgLoDLwBZ2gwd0zPJZRKhP7f8wlUJpdmr+fMQjOR6b6wakf1yeY8O5Xh7ppDZ2u4aV7/GiExoKZqP3SACgBg==