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
- cd509803f18dcf5b42e933cad50d364319f6bec3a8413e1c0c56a6459ef58cd3
- request
- ed2cd0068faf88bb0d5cab5276e9fa602a19504642c023c6422066a03a4a84de
- transaction
- 705c93ebc402fd1da936489564b38a55754ee6a5dd09c0c43bc36d630133579bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73273
the chainentry 73273
- sealed to the entry before
- e3b10d4f2d3288dbedbd496dd721885a707b5dd13672453ebb098ead2f4101fd
- this leaf
- 3d9dc8d670ee257ecc04a2231e7dd8f22ff0baa738a7396b76f4ed3ba36c88f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m/J1mWvGLaBudnOhKYAXLdj4+iR3h4RG6QRPKvQ07A28Jmuqd44OmtsKkBbSs0mftpjxMT+s/3vb3zBN0O7tBQ==