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
- 8b6851e98c406731da65f721b53bad56b9fc194f9cb47686331bb12eac521451
- request
- ff0d3bac1bcc3623100cd208a9f0d27fc21d20226dad7759d251288c7d9f4a59
- transaction
- e70f0c2885d59e85322e8d7ffd0b5eda962f3a852072923dbac5744992b66d74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70616
the chainentry 70616
- sealed to the entry before
- 5b8f04719d091bd33566456392f6aa37c16017b8f0fc329f1c50490af25c8ba4
- this leaf
- 8fe486beabf765187d469d88bf1a0e2229c42c2c9e988fc8b2942330ee49e839
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qwDSymE08JbVBKsK/RtXbRxb3zBR16BWqVJPUb5vZEjoCa3dyFH3vuQPBzns8xSNErwfDGbo+VxGH0e28rOvBQ==