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
- 390b170bcd2c808a66ed0da241011bed5b045012e6db949d689a2df6937e87aa
- request
- 90bd351124325528b1b285c78a10548072ddb7061eb7921863509a16231841c8
- transaction
- 372a663e2eafc80a13f53a925038cea4ac414144709549d20b70cddf2b0918a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5679
the chainentry 5679
- sealed to the entry before
- 9d2ae4518ba368d519e7778aa7e25e746f2bc1e15a32106d6dacd9c1db973720
- this leaf
- 573a708d330f7a2767876909459113b207bd937aa14b2bf1e955d597bc61265a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0YJ/+3gGZ2QQOzD1nkkPTPugh8VvI7ZIgvdRhrMxw9o6F+8nyLEYRZlL11MC0ouycg/3pefOprnyAUw6FIntDQ==