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
- 944a2e37bd749a12639caa683f07bc57c854ec428ae106a10b647c9a465caa12
- request
- 67ec69798a1d9e76b7b759a93ec16cb7e0c9badce5419cf556c44e787032bd01
- transaction
- e983620c7615a87a2355918e80e3b6ae2dc9a5a939854c0ae8bf86875fcfccf5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67259
the chainentry 67259
- sealed to the entry before
- 8659bc5277df7ad07a8de99cf421b3f6d460490c1477cf13353e084b37c97020
- this leaf
- c4759612a9cf8a798fb1a313f043faefa370b42c22ad6d2228e79b4b9b5e267d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JIfhT03snFuHafuJLzGCB/fIHt+lBfuJyJ3uFj2EfPgLQslfCuG4iFRxLJI2pBn8Ag2Hcczg5RFVbhSzvPEtBg==