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
- e82d0215488017304298a20bfd8ce83cf34b0ad4218ec4469693e181d98e3985
- request
- 033cb18c1e9a802fe558ed6a2b4959b0fc58db7bf258300de83041017b411103
- transaction
- 6079b6587676e3b334c3bb1121686e3f70cbc9c1e81ac534abfe94c3ac3ff8f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56
the chainentry 56
- sealed to the entry before
- 6fde2de001a0a9a09ed3cb628c502b248233f00bfac54356017ac5868fab7258
- this leaf
- 37c7859672f2d19504bde8615c8a5ef737e211bb01aacd6d767f9f38617c4623
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x0v04aO1DhEQ1uu34GedIPpjKqgxFPN3CJ3vTehRSI3fGXEyZqQP1fzgF+B6/jQPPanDKftmd9isqfcuI7nfAQ==