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
- bfe6fad1ec3a8dbff9b74efac324385cc9af096d42e4caabc409ce27befa7dbf
- request
- 64ffc7048ade2541e5f8bbac4719431f8fd2a9dfd0189395f601540e220db277
- transaction
- aba9729b664a9956e648726851c4f41f9b932bac1e22957c3aa37acb85e87aa8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17822
the chainentry 17822
- sealed to the entry before
- b3c863b25d4633fa3e41a34ffbb6afbf2e67093a3ec6aed94922ef65c74029e4
- this leaf
- c5af256279dc8b09f003d9b967d0e4fca409338c38b7cf211a89f5f32565fc36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0l7PDBGR1XpSlvQKZWE+Gy7UXAkcOQl+GKUnTkwll6noPbNz0xg/nfRWTy+KgQNj/bhiTfXf3iYNgHM176iFDQ==