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
- 369bf01a69d333dc4cb26ccfe116268fe2efcf8ea84c1d14852fab2a6e16e6de
- request
- 66453fcc09a26af052be92e58334cd6db77b725be28cd49759c4b67a1650c79b
- transaction
- f392a1eea2f8f51c8de3d8852afe690f286f2d134d3783f4da16af5eb7159f50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1755
the chainentry 1755
- sealed to the entry before
- 596d340b3c31dd451e3e3199e2e64a53d223741baa9b7fa72f88eb2a086eb37c
- this leaf
- 046519793022aff57f3239e99361954137dba60bdfee67e9676891c8f51316b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nv6fkEIyoHK4Wilzm9to5wghu4lrQnZdoX+KEIjGRj8zBpKpuJNMPuaOYVuANfVPmHZrqYIQOfSgMEGR4JvnAA==