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
- b7b8b01b144ed4c7f747dc4504e90beda0e86e0c3171832d5a41887bac8ec9ba
- request
- f773e6ac1fa7cfa913db9ba88c6fa4de5612e4c1ae973df7b14b8c5e1fc1fa43
- transaction
- d0b95171e987d66a79539b13c129f1b75b39217a1f973f7a8084a75d8ab943b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4197
the chainentry 4197
- sealed to the entry before
- ca0d10fa479674fba9a4bb0b367efbcc51821412399019b0c88ebff6b87238d5
- this leaf
- 9f9c14e1b6d992a1c8fddff9a4e05b4d6eb3eea8f2434e8b96135bed94bb7fdb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PA5LnrOH0+Vu9LDHNrjl1kd3ib9J7BVEh80rzAt9mfjiUUK2/W79F5Jo1kzkQzPkGxzTWXRqhDkzvGP8jDiTDg==