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
- a34a846c4b09d30906c0f21f8a43708674099b2c9ab823f81ec8ba53e605ffd1
- request
- e2181014695d609140e06751c821cbf494fe59d6267552645961a4f293d414f6
- transaction
- 49c28d2faf6f8775467ad11c3ea2cc0ca86f9c336982bd6b3f0eb948e281d832computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25122
the chainentry 25122
- sealed to the entry before
- 014103a0a9012ecd00362018cd26461b26ba973ba8d5ab678ac071c024cbc9c9
- this leaf
- 1682a67fd9dd9f8bf1be11b2cf7eaab6eae3d566da8c51bb47c5cf25f99edbe2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C9MaKaTEzS0HJ7QyFbYMRKsIhPnNpMwU07jdjtHRVQ/TTjpbwGg26MZ7d8Sq6QoUWcibCokW+tLkeNvWEbbJBw==