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
- 487dd5ea2c1d74bca191d03f51860d83f4e80eb1aeca3e520dea2aa4d6312d38
- request
- 7112f14641d94dbee60ad4b409ba43a59117c506ed8682746e25ac7c9584feac
- transaction
- 961b47c89ec76d63597cedc448acaa870d7863dc20860e7d37101e952ad4b91fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45778
the chainentry 45778
- sealed to the entry before
- b901ea6859ca535964d2429b8af65a91473cd6c715b831130d1b0c0683bc1101
- this leaf
- 69f880f394c8e227751a1366151e59d451136d23ba023b648512365fc6d60385
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KlF7og6uzo5KaEVHcqRlAtsJn/YzhqZ6Tu+uIjoxccL1+t6jNvS1mYFDCicr2l8eQT+VMN7hBc4CMYY32J3YCQ==