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
- ce0c03ef38c2970976ad6f07eaf1de3cf45da221bfe5de3928d56607816da124
- request
- 55f7cecc78e8e4ef017bd0b6e54cbd22df72017daeede07946d0cbcca4bd6ecb
- transaction
- d868c964c3ffaf9d2884c8d09c5e88a1e88659999240aea895aafd96576a148ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34341
the chainentry 34341
- sealed to the entry before
- da41a8367cb0c957bcce5840bbcc52ebc69344f805b6521c8a5c42b35fc7a4e9
- this leaf
- 4f9df3146a84d1b0f255776bbda1410ec5d659fa9a2a9c162b6e4a5089e8cb92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Vs/IH1i5tpg/hv3ud6T7ntLYj+NlLQWNod0phLAdSUd6fXc6z6SJTfsqb0fdvf/O/QVY7ljNfCdbsISCxpZrCw==