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
- 8fe447f90d106d0ad3d75292b5653ce6fd11243bcaa72b23bb4370e1a5c9d9bc
- request
- 5414e8bad7db89696bf3d344fb4dbf05f9f42714ad538c54b25bf5d7e0b3116c
- transaction
- 7465a5d512754a0a74287e98aeb9ffd3e2d101c9492c36604e89eb4e372fc85acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50259
the chainentry 50259
- sealed to the entry before
- 53259a3ccd9a72fde6be5078c9e53233b7b157b2fd50a340b93369a077f5d2e1
- this leaf
- ff73972521d1e9cc1b38919cbf9a42fff8e0b982e5c6aa18baef8ee152f2257c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Me32p+l2rs+Q2l7bHlkI3ODtVUr9nYXKeuAIIbhr7JGpyChJs2WGz6Q1EqMB+ZkkAIRNJvSKgf2bpsh37MdAg==