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
- 0a1eda7861ae4427a9344dd5cf009434ebd167994589749f39d52a0b02b37028
- request
- 74d06d46afd3b7521ee10b728cf1876faaee3f05399c405da5ccde0a1e309c56
- transaction
- 606c4ae68bfb35c8f2f928954df4fa6e22a7886d71454441eb14ba176502aab9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22899
the chainentry 22899
- sealed to the entry before
- 2462a85efb8d87a6d6d2ad5ae87a852dc34739d6d51ed07d6a45fd8495b39514
- this leaf
- 37b87a2480374ae2fd893e8688d58e6ba9a0a857251c098da715c63ab3f8402a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6bsmpfLXnl7QblxeEmBS/CoI8FwxpifU9qmmz9HNNcZ+TckltrH+pgxyrTuFJqDKfsO1NZskOkXteziR36bgBg==