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
- f861e835e236f63688f446b849eb1b2458a95cda2fc4c6268f562d17f2f300de
- request
- 39888fe8d222a6207ec490a92fbb076cc6d4169ca3ce230f4f4bbcc779ab7491
- transaction
- 85017be9f111ae64bf659ba724dd86111483dbc4bc3b562fe46a7686263f83bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57522
the chainentry 57522
- sealed to the entry before
- 649351885eb2b71053af614f68cb825c826b0303a87c740cab758af6f58ccb25
- this leaf
- dbf434f37487a7116ca6bb8789ec5f54b5ebcb56658c69962323a975c16793e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /qTg2fm2JF83wD+2k4HCZXgQEO8e0qZEqCDs1R2sLzeUs45T7XB7dWCOWfiVNosyH1YeVG+LO/CFzvyVb0WwDw==