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
- 3efcb39b228c656fe509e2e4c70d8c9d694b0fd3cbdbc292bbdc0180b06db260
- request
- 01ab8b5c6d354d80d671752be6758e262bc39fe121c5547c8b712ece7e26ab94
- transaction
- a097eb21ae127bb0124e86bb806ff98d3d487ba00fc6c192a675e1e186792fc0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50190
the chainentry 50190
- sealed to the entry before
- 934dc6d2150ddf3cc56015cfd2eba10a1cb72b921436cb08acb45aa04fd50b99
- this leaf
- b2e2e4c3429f4ef155634e39d4ccc364956ce69944bc9c2a2f4e1390eb748055
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JBMg4ccfHp4EulpspwgULoYXBv8UxHY56esG6u7dgcxQ0em46h9deEFRa5Wx+NC5K6nbBvUr7PbF+eOW/pMhBQ==