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
- 7245e75c17ab1aff7d7ab8f9b3d074407b3f71a68bc44b436148deb70b42b48f
- request
- fd8e36a1fa86bacff034696466802ca5fe2136c358ec2b1e51233664bdc157cd
- transaction
- eba77a70622bf63ad17bfe9c9d7b3d7b189d02c2fd24e9797fd78df618cd2ba6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16006
the chainentry 16006
- sealed to the entry before
- 680518987745b522fdf45851d11007d15b3c4ef8f4d56778813ed9283c5a8aa8
- this leaf
- 204d1df106ce474352db412d97eb02ce492264516ea66bf467f374e0c36f9608
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- viP2UvDYGVXQvk6F+T3TxjxSRU3kr6JaA84zcncKgjoaV/HCIvncS3jYep8auQ814JJ8Fu8mGGEykBVDsbz5Bg==