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
- 39a37722e2e3bda4a390e39b4353f222fc843a69d9e741fc05de5cefd4f68e66
- request
- da22cca5fce5880ca6e8ca3b6554671995459bf5e4440c58092796c842c6ac73
- transaction
- dcd5dcbb534a149842b44c24d9eea37303bfa1975d0292abb3028babbf70831acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44434
the chainentry 44434
- sealed to the entry before
- a8549b8e2ba6da02d97f91dc5e94fbf29b2ea639b5a4aab899ac0e9b90482da0
- this leaf
- 8b5551cccada7aee344404810bc630d64c6c5c0d29fc8bce5a7d15dcea3a54f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s+GJaVX/q1TFjWS4+R/scByPG5WYUKrznsJcnn7A7FVLcwuVZ6dqDo9whIKkkQUATqwIavdCuvcxaJEezdjcBA==