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
- a8b387a7b83f103bdecf784a7ff5c7f7e9c4a9db8a09c40c4ba016e77fb0bdbe
- request
- 03e27bfb8dbda7fd4a878eb06d658ace63488cb7ab0cbaad96ea9d751f028942
- transaction
- 8d352e0445e03ed43aa0d3670d83f4d1e696ed6899b757809d05efcbf408a287computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70633
the chainentry 70633
- sealed to the entry before
- a03eb12876cbf92dbda5208d0e11375dafd38e2662705b16b84bcda937f243cd
- this leaf
- 17646952db5fb5f6cfc2126c26feed25a63532df6ded6831b784d38b9369b0f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0fSCbNBUuG8S04eeoibgkEPnzA/h5kdgEv+ymR/+DLehgZGycmyBbzbqGUhvUJaEuaYFobZVBF2SjKMOrKtTCg==