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
- 4eb508a43cbf9828ba0e5a647dbdcb389d00457352d7b03231e11e03976c21c2
- request
- 950d5696ca0033fa0b7b789383920b7f8d0570fabd8e2691a5397d228a154934
- transaction
- c5c042eecc3404fe0dabeceb85b2e738e0494a79faa5c504936de4a76e428b1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45006
the chainentry 45006
- sealed to the entry before
- 437f83ca33d9ca9b9415e7ca841a08801a13df306275b5cbff4c146c2aeea48b
- this leaf
- 1c0cf7318839f2bad7f68ca5a8a666fe7714e6842e8f2f47a28054cc872940b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v4JJcEdDIikS/KmSrVImI+7SzBz5mgaOSPR42fhRdzXNow1JMBjxqiRZK5FcI5Ej2sG88XK0XfCK2/OF55GBDg==