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
- d12decd182b1be6de9ebedf300a137950185708c8b3a64b6a23db078c82bf9c0
- request
- d984a7a876f791e0d78c3a031008400511e2d3d65df0281bc759c76bba555982
- transaction
- 5262431855637d8270fb38f22ff00944f2cd3460a4a553ceaf4c56ee97278341computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67893
the chainentry 67893
- sealed to the entry before
- aa7364f60df1caa85f6416e3299b25163967745ba57820b44ebb611c977dcbe5
- this leaf
- 60859c1e097713a3d65967825c7a748144e7f598c6a2a30c65d91da8c45ba879
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ngWG/hfFDFUgvXOlrSEdinNSMJ07FE5W5wyAsSHJsPY6v9RSzKkjSKlcYwb1ksfWwXXi99XzJjseys8hYktiCA==