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
- 5f95c5a4c908fa5ecc3dfe69ef87dece74e0317ee6ded308d7f32cdcb745c6bd
- request
- 3f3ed64578085b4de585604440e6f5c5b760d622fbc8f21c8229cedcd389506d
- transaction
- e4fab6aac6509778a8d3ad56786e649542836b9733990d803039cc59a0ae4a4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15641
the chainentry 15641
- sealed to the entry before
- 845507b1154e7235adec284607a881b302ae6e81bafa2d7cb4a07d9f484e03e2
- this leaf
- ef62861932b3dcea5fb1d0e46a662769eb946a3abe7b7d81934385b13a594da8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W4paavb8D25EQ3NleBoWbAKNxBOLztVdPjaCGcy4CsEU2X9piehipXDlwCcwhIj8dL1GuIlmlUJFfZLCeTBBDg==