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
- bdc8628d279ef0bbdea69b9fe9ad7432819e623b79b9624c0561d64487d8ff93
- request
- 4ea98b45752d019e1a9e3ae4feec74d71be45d05e5aafda77017d38fcf53aa04
- transaction
- 60223462fa104c0dcdb0ed17e9eb4ef885b24d86fe2b28f277883362c0fcde84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23501
the chainentry 23501
- sealed to the entry before
- aadf469e9c5e80d5dc1372793dccfc74a267a2f1ec9378e24bb584c711bc2935
- this leaf
- 1da0b47c24e5b220043a371c23a5fe6e5f6a26e3ae8cc9cf685a1cf1cb32dd87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QLNx5bfSYvsQ96TfteWDSTZBCwcCoEXAsnPQ4WxQKMhaD6WnE9gRrVudVW72mHL1Xbl2b/cs/l/jrXyrjbSLAw==