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
- 3ce93864be64746106dc47b62cf3c2c448c47119eb55c22c8fe8e33383f90047
- request
- c5dfe69f3a8ae622ec16e3fd770344f45e25bdfb64f49cb1aba01cb9ab144023
- transaction
- aaa0dbf98d32d558a985a6e162bb30bc14bbb27781f031f3ee2829d79aeec44bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54573
the chainentry 54573
- sealed to the entry before
- 7bc6d6a57a52aa815bb244d265a0a169e563d60258d2cd6c9a0a7f0da29b6e37
- this leaf
- 56ce1c822b6b196fe35090531fa858b7b730e2da3c98ce8a2c2a3b33bad5123e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zlNZFsnd1nwyOknNFRQWUiDwXACTxSpkDoXUusF1+fbomJaCKIKnhjW+mZR7H2GEL8DBrB+1eECf4tsydLI3Dw==