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
- a951e91e7903aa8344611fe904dc3199325d81ac013549d38c83de7d8d697708
- request
- 92a9af60cc54b61407fff042dfa71c7268e05052ace5b9ca588ac7364244691f
- transaction
- 2cd04fe28b5119ad8d66802e3f0baed225fd6accd6ce89a59a44a1b046db4f35computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36024
the chainentry 36024
- sealed to the entry before
- 2ce1e262077b032f49738a34a8275e78702bc42ccdfc1339202691a390044351
- this leaf
- d27efa04464e25b49026b07bc1fa1dd36d131b44932bf66753b96f2ae133465a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6egSzs0S8hhsScPdZa+UI8t1lZZ9oq9Z2IyBLhEU87uRU3/ONZe37FYS4QzvK1TYefLnVOltB8R2WF6eLXglCQ==