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
- 009117e4be86b578f4a30e44e4c07fd4eb84f6d452bc6523e4f4c5e8b80ebdaa
- request
- a55222318a64655d263342a7cd637ededb5faa6ccfe2b8094301e695b3c96420
- transaction
- 4661479b710a5ef416f5847bdd1732090f1043fdbf8cf2ee89cdc981aa8657d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37916
the chainentry 37916
- sealed to the entry before
- f6ea171bc3a6655df907a9f96e2face9bf2906151c09c4791741462ed300cdbc
- this leaf
- f11bbb9901fc73010a08e14c18fbe9255903209d615084b9f595999d4de4a41d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EF7I/wv+1MPelFpRdGLXkK518KW9URXORsRNCcqbuu546iOue8N72K5W8PNymXpBVIdLMizxc8g708SWKLujDA==