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
- c16a9ee714585a7436118bca7cebfbc31e0a99e56b32a7eede1a8bdab103143b
- request
- 93f303f67919d42cc56d4e5a993a9b3137f97342bcb45063a70faf20c57e6953
- transaction
- 5a8f56d6705b792a20727a336a5273ae168dbc21e6a9be2c0998e84cdc3a3bc0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55670
the chainentry 55670
- sealed to the entry before
- 412773f841cf61b2d646faa0821a4ec927e6a9f0ae2f652a920f1bebcc983062
- this leaf
- a1b9e5562ccd08ff3eb0ec66d58e4752212aabc9810b4af33d65735bd3ae1d0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- abFF10SbXpB99nQhNOccn1dGa6fKNdRO+D4hsYZ+gqLKF9U/Uf+cmyB+VadQxR41V052ZuNmFYxYOHTcbSurAQ==