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
- a3b7e7b8a7912e4450a76a7ade3489e674dc1c82de27824514eb2959db389d90
- request
- 528710eaaea44346172e2aa4e99078419ff46a647ebc44cf233bfbb321301264
- transaction
- dd22189597d2c9b0dbb9bdc8c9198f0c905ff7ceb47bc63688e407d5a0daba20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51255
the chainentry 51255
- sealed to the entry before
- 2a8d5a64bb6f0b915ea8d6bbba70bb2b8fe4637b5adf8b86874cdfde6a5812bd
- this leaf
- 4bfc0af97a40fb2162e067c439c354e59149607bb4835b67b4d795ab7c3e6a6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4/gfkKh9PH1Kf4WwIJ8Q/0KXYZT+V7xpSSjIHuJnl6FKXbVxoNweC8A5NhQ8/ZKwF0MeFNBHvr6QKnt6doC9AA==