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
- 24af61d77a3c6cac921693b85ca9279f4d6793f62416ba5f645f33b23312be11
- request
- b74d70dddd039de1096ed71caea320c7906d7f47ca66c4911a03988ba3338ea3
- transaction
- 2dff53b4c131e6d4f20bc229ea982bbf9667373bb2c98714d10737eb20955086computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26886
the chainentry 26886
- sealed to the entry before
- b409eafb8b9b018ccf8a1cc3a69d25adcbe165f44519d3688bfaa00ee4cb14c1
- this leaf
- a6821e5662012f20299eab879130f8ec40bfce946dfe9b06b1825f5626e4de38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mYaNEwwvaikdeuYmBS6USrfBqMs2yOpJeLAq1kvOu1+CeDvCavznMgUqK8lcA2jUKY30N22zdcQFnf9QrZwsBA==