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
- 7a001ba648534d0a5ab57f81ca97a37c4c865d6505d7ee4a204fd5fda3c7f966
- request
- c629576fa9848d60784794b1718960723c095444fe7f3311cf04c23ff341ed65
- transaction
- 08196642d325e8c44b43ad6bbf9d3dfa07d497b61acab1a8e01edbf2f3562d9ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12631
the chainentry 12631
- sealed to the entry before
- 9b7e65426d007f690e0547f30267817c5fca0693bf3532e3409a90526e0840c7
- this leaf
- 095a3f11018cf2d5d5971917601fc4444a991da7ea5ebca64d511ea1e271d3c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e9DGZovgNS7zaegSkfWo76Ks5IejAeXJOyZFTThX9s8VfzAPkMZ0NYjBw8lxntLWwEUYF45em2HmAOy59z52Aw==