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
- 0c3f7cbecd72a877594f4638cb1f2d428fb60e670546de997311f95256f9f07a
- request
- 4c1aba50996925fa5da3783ad4479ef39802d3b5014a50908f1dc588a6aeaaa9
- transaction
- 96d24133f393801882708fdbe6c7de6821bd7792607788f2287ae8da14827abdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7227
the chainentry 7227
- sealed to the entry before
- 4e977b288839037a1d47c63b00ef45e6d7930d6eebdb4765f36e24ea32af21a9
- this leaf
- fb31f8e602816065b637cfc98417673f5716815517097d8256e70f7eb507bcc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hc6+bkVi1C31EyYnDYMaaMfcsQkcDOmscbPkNE1BfLFLcbQA0L3Cgq7tvHv+IDomfzis5aMb2AiHVJDU1NrhBQ==