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
- 034951188c2db081390e3848d1952ca0e632955517a1dc8ae88047bdb238995b
- request
- 79c187901d63fa27127fdea79803183fd2d2579c2b19ca973545c01dcd318514
- transaction
- fe50e714516a595cfc6fdd85909f05b39b31a31acf0cac83e9a155448040eb12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47516
the chainentry 47516
- sealed to the entry before
- dd3ef46f27a7a8060f4f71957a70d084f5b785ee776b257fef32a3ca81835623
- this leaf
- e6cf839648439f354d3c9c740904ba43510ec9653f56108737a5e586b23bab53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0ANqz7JRCoO8HWLmhiDBtiogZmPAQxRuoRUV2P66tzinn8RhxokewFQ7Oaua4MfOTGdkfYw/oRot4Gg4vTdoCg==