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
- 28a357ee41efa3a4deccb166e6312fd44ac2d04048abcf4fb063b510152aca15
- request
- 1a63fa6532c9b9f28a372e4472c267bb93746335cfaf52f1559dd639de2bae57
- transaction
- 04d4d380247d1626b387f51dc054000c7b59d11ebe4724bdc6f5aba7ff480e73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20711
the chainentry 20711
- sealed to the entry before
- f47f5022d8efb88b04179ec75159a5db7caaa526dd2ffe4be16b73745019a6da
- this leaf
- 5a124846fb3c861698b86b43909e43fbfe8cde2675a402c0fce32d76016b0535
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IcNVeUF0+xo6K6wIVRZHXueTcKLYYTsKi2toOe9hCjfKyWgfNR93sT0lxptYnjey21ubG4waAPesQZLbbxUTAA==