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
- a58e9f95d5137a32596b892602a0637651fee4ef3406685830b132509517dcf9
- request
- d5b3e9ad490c37b21c04df4432f5346507f06e21554b45a9dc7e2428c8a9d0fc
- transaction
- 2c5f75e7ce9ab6ea4ce24effc86534e47100c852fdb7528730ac7fd2af1a7687computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 706
the chainentry 706
- sealed to the entry before
- 96db1247dcef2e892f02d12322af146a6e891b7e1507845cd3472e5b90cde44f
- this leaf
- 327724452fc50fbb7751e7e1391e120374547a36d735c4e1bb5fce53209e68a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HS4WFBUFCq9nzFdwJYQTiu9qCbc0W3m27ZzmeQ4FZkqBu2ik5xIgN7JntSPihKQVlZVxqDWWAKURrsg4x3NGAA==