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
- 87e3e3955954578285753b228f2d1b25e095ddb7a9d75a0aecc345a2cf7bff1f
- request
- c4542f96566490b4480d7ee0ba1b2d95e11a1b175cfaca536b9f1b148258ac24
- transaction
- 0195d908f92876f67ff2ee06fcf6836caa35f5330e13208b3b4f70e270e36efdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20347
the chainentry 20347
- sealed to the entry before
- 8c2b5ddf1650c70d8bdc26bacda67d3e88ca59d2f002f1effe070473a5622129
- this leaf
- 06401ea13ccfc0c0c3eb6467ce670e99fdc8eba41cdc61877704cbfed14773ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vr79oGnnZwxJ3pB4e4D2PavcCnVo/CJ88AgoVF/4q3JeSh1vTwpW/d6fJFO8Ta1EhT6+gUKzeil57ZfjOC8WCA==