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
- 3644ffeebcd842ce49dea82d7fba7b28132ca8620f7bbeab709418007f4807c1
- request
- 98d5e6de1862959f35bc950ed2540bb622bdf8b9e194234a6ff5e490ba98c906
- transaction
- 4bd96f88caa308fc6966a005912928828fd08d54566e85b59b5effe99818ff0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47440
the chainentry 47440
- sealed to the entry before
- a36a79b27f437d30b2a62ec8993c43e7306b970dd01b7ed7a2282594a6d8cdb6
- this leaf
- a3e1080f0dd6ac3ae16e6d5c775c45d64b6b3d44a83e6f270ad8ecb338bb0097
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 76W1FF57IX9lxpApV3a2fhMOxRGUz4eY1VWVoibay8tiF7F6VtP8Jm/i1QQzv/50hwT5ZCi2BPBbxbEKCCTyAQ==