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
- a4a1b4920257568f64bf324f1e4c7df67cd905e78240bcda032d8db494ecc261
- request
- d620c1674a789b4155049801a8d9b357a34a619404b902173d9c731d64a23fbd
- transaction
- aa33c9944d299390473d7ff8821bf49788b0fa3c4522f760589e090131aa9a7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39770
the chainentry 39770
- sealed to the entry before
- 26f0608299f4587d625886d1e95e0a3ac85836c7d8ce9311a6d17bf8a701d3bb
- this leaf
- 5ddb4432ab6be949356d926e9e8c619355916097ff04775a29896828e7e8ea0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VjclCY3zy+YoVE3b48ui5bx6h0OZnzORBmXgfGxmPsJiRzhsGdTvWL0Yg8PEvY+8JUUUu0wC2mN+31moghNXDw==