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
- 9b6155fddb322d2d600dd7225cf38fc3a613d917a87456100589f3ef50335a38
- request
- 33fb7c4176111715317903942df5b73f04ccd1fff9c64c4c06d599ef27d8b0f3
- transaction
- 3ac75aba11d5cd00cfb63c45d4251e488be2bd903aa56d0df040c554e5f92898computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5903
the chainentry 5903
- sealed to the entry before
- 023546dee792a69a273cc484d0729bdb84b0edaea5df87a73f67b2ac17a822de
- this leaf
- a2a71c80d9d00355f25c59b05cb54ea989183a418cc1bab5b5578ab95041ecd0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LSv76XfsXXBVR9kSSQN4VuGECf3k/DGLhK7CrgbblRLCNy/wlb6sWPdmOvSpAv0nWoYNPKMih66ZxdtHJv2JBg==