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
- 48c1a5c80f63fba4d7becf5cc3a8850956a9caffbeae36682530714eb752e6f2
- request
- 89298973941d137b1efea157bdccd60267c862c7e799af40d8b57e384dd89454
- transaction
- 6de87c000723e6252da80873740d27a810a57c900de93cc99b1d5aea3710e3b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14999
the chainentry 14999
- sealed to the entry before
- 08075483b8f627a8290805dc566203ebf45c83f30483ed7800248b3e3d283b98
- this leaf
- f03a21c564b719e04b2d03107d4430640d5bc623de987e96296fcbc841bc8c86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wke68ccTANRkSNFSy6twzu/Sq0TvQbKYmMsbSCCACVWnl8Ph5Hy7eNpEyjrq2HYjeMSWH+ycr9e2n3jVQ3HhDw==