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
- 622c652c0c9871937b7263e46e39ba6518f3f45f47e1fde9885f4bbe63ab4ad3
- request
- 09f0c98ee2918d6749d52d301907a44b0e8627241f09eb686a1fc796724fb68b
- transaction
- e906d87c87bcc04c7295b86d10fef5327abb48d3719000d361b469e423ae7872computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64682
the chainentry 64682
- sealed to the entry before
- 6e55053c233237dc0542d478767e3c21f610f63c72b7fe46db489c0adadf959b
- this leaf
- d3fc58c57f36369d1c1405a48df6cffa65068107e7752e4962f888c81dac9a4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nqjoyK/88UecyVuuSopycTV3uReqRmWdvN/6RAbSLaD8CAiuNAbmvbHxwcU015RHUXzA8rNmUiNO4LnJyMp5Cg==