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
- 0a344a29fa45b1597a384401382fc705318fc460fed68bd3adddb41a3550092d
- request
- 62ef078c4dbd5d9422a5cb4bc99bf111683cd9567a435cf37af03254249796a6
- transaction
- 625409fed8631f821167902d31493e7cc5c98966c6c03b4bb54e46255e4c9e2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74100
the chainentry 74100
- sealed to the entry before
- 242fc2f8dce9f5fc4c87ab4aaad181eb07fc4aa7929029217765ad09bb2cb75c
- this leaf
- 00287753257990e3c7434a59bb6f4d0d77bac4bf756021e4f1f578d9828e3770
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ncHreYfhAN1DKu2W59fNV5lGPNASkdyBL4tug3ES3rp/uUk/LlqjA6VJzTrrx1jf5EdNBg1zBOJs9BxSIVvQBQ==