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
- 0c20cbcabf9573f3b18137eb43ce929e46bb61b509f7440642e19191daaccf46
- request
- 6d3e3bf7eabe92bc4a4e1f68bf32936c3ad1147887969e3d9a592e0156669940
- transaction
- 6a5cc9012335cdb1c2e54f4cd8546848e94562ff2df4320e857d09e24db8a789computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59663
the chainentry 59663
- sealed to the entry before
- 5fe3ed97502ca6994c8123bfef3155f6cbbe3f576c4a9c8dce0831a57c298ef7
- this leaf
- 9019162b9f07c13b7beccd528cae64976e5e84a4d0f38995ac9ab4adf4c86c3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7OCOW2YImkjFhYpLioZd8tuxz9cTozNGUOAUMM+L1/A4pmGhoaFpyU8WCNAjJRdlLLXo/oGjXFTr+CLVoEr9DA==