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
- 86dc0d2115d8786e586a85889541b6d61bfa686dfa6ceae1a671ab708e3c133f
- request
- f531698534632c67e82b5ed5c35f3c674ab33f68026bac2a4b572962a5995632
- transaction
- 1e96ce38c60ba881376733d2a2fed8ecaf833ac44bf7d979198526338dd6960ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21788
the chainentry 21788
- sealed to the entry before
- 109ee918037354e0608e2c4b0dc9e4d4997050f3bc0a16b1f29273d3399f0e57
- this leaf
- dbeadb0935f5410a16cac42e5cae5a7889cdb3dc8f323caafd218bc871887692
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q08ydgogUjoEOCNNAIKx994+4Oq3PoLdIUNxKny+kULPwrdaje37GWqm5oA15nFE3EAo50tgrV6NkGEYN5hSBA==