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
- e194ef54ab717334c171975e4da0071099d3e6b4e73fea79b9678bbc92ab3518
- request
- 862e1db67e22b9a9f9aa3fcd8eed9fe43a4a90e87cb458fd9d6f29738b91dc04
- transaction
- 4c3aadd4d59d221a5cf9fd1313bbe0aee85249a6ea7b7f31b75b8f4dc8967eeccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44368
the chainentry 44368
- sealed to the entry before
- 3bd92cb41c5a277164cd1c768fe89e2c01d455e61d4759281098d3dcbfc07a91
- this leaf
- 8c81c74298b8ad268e6b3adbc35907c36e40315785decaf6eb95d541fad16620
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cELxcJrVUsh30I2urdblrOAcpF943XU1Qgv7AnfiOGlTxqL9oC6qJNnGNIhB9GoV2Lxxg4apiR0lRRAmkDGiDQ==