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
- 1366a01966630c456a9ceb4d9468ace8cb42a0630a038899ae25dc900ff05ac4
- request
- 2a8f33a12c621c4bff4dde7d82032ddb23759d52c374da066a3d49ad3eb04f85
- transaction
- 156a131ed40c34a14bb42fb83ab15c59c5ae04321393f87cdfb342cfbb6aea0ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10966
the chainentry 10966
- sealed to the entry before
- 0e48026f10874dfaa7a5e6fdf01564d604fa74a57187e495ea59ef0575e3bc22
- this leaf
- 487b434d74bd54cfe7d96619b13c6cb902badc9be89bf9f51b81dfc5c194dba2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lAgHYXLEcVAZl2pmer6Hsq0ks7s4XlUASY52DGCEHlxmXhAZ5ikjrL5m1QNTd3m59mfIyEuBNxAIvPqW3yJtBQ==