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
- 584feac021b0112929c9969bc2603b6ad40cb18e097f315e53205330833dee1e
- request
- 0af39fd94e27c211436c009772923fbefe0aae44372cd4abda0fdfb4747acc8b
- transaction
- 94c4ee191dc4d873f1e26a29c124afc02b5ef2972d853fd0074431de4abb50f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8105
the chainentry 8105
- sealed to the entry before
- b1075ca2cdd91ed952d49181113e71f15c02d24585ae4fde69646bf8569ba576
- this leaf
- 3d7e3c98a7eafa48dd15866d44644604b863080d2eb852c1cc60855c6b182693
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 86UduPNnRx+B98RNQ4czXCJNrMoHAxcDKKkHfKdirCixAZanCH7elhwFx66ZKD9aS+hIpOJki4/1AgH9VnhvDA==