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
- f83cb98f4251e73cc28e6722c66ac081f5ccc694803bbbdbe9b90af5050e599b
- request
- 43c9eb3fc46b45cdc7e82469845a999bc1f8e316c5ad97f0f9945cc2413401ed
- transaction
- 0a94728582a49d7cd197792b91046bc1b10608ae2ddff2bcfcc238c2961d85b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27176
the chainentry 27176
- sealed to the entry before
- afb23821a87fed8345a1700e4369895c7e2b9a980c7a9f320f6533b44ea102b5
- this leaf
- c334ace111bcbb497bf6d3739e096046cb8f30919bcfce115925510b1a79e52c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JhOahMSbhFjY9RvZ1YVTpEhjhE14CNHWtrSK1gBHxXitT9QkmzMg3iDwhnPOSXLlq3grJF2DCsoD9KCz9yTICQ==