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
- 410030fe6b0b63af73c9be67fde416892d823ba6dea209e9284ed0fe31d42b30
- request
- 161517ee53ffded8bee4c43af498c006e0b93babf53af40483cecea0bf9d93b6
- transaction
- 501b5802a693577246a02bca5716d3ef2ad3ea7cba3cf41b4375f2386612d1b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32357
the chainentry 32357
- sealed to the entry before
- 25458d6100c688e9d2fa0b9a4b729268bf3ecd955faf081180ff1e13f4f3c6ee
- this leaf
- 935a9410cf98a6776c245052f7909c1637925e88fadabe9c2db874c963bc10c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lUmcnWg6/lFsAUO8y0acwuEkJM9GQdlbQJ3P1uvIPbUwGjE/8kTA4iFtSQsqUIzp+DWq6kIw3f5X5HhG3hFGCQ==