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
- 8ec07edd9c4f4391e28c44adfe2499076ffd0c99b21c1736f81db722b1cc5288
- request
- 9b8f0322ae57dcbc8f055ab2d28e1b0e092ee197e13ceae19f005f03f1121b37
- transaction
- ddf6b912627818107b38045c58f575c4158eacddf2259be3c63c629bda4733d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72215
the chainentry 72215
- sealed to the entry before
- e6000f49e70a3120053ab8b94d68cd2f021a48a5ea1b5858c4b865a70dbcb804
- this leaf
- b21cb5b64c757a724e066c13c99aaa12c55bc8c17e2074d3895da74f38b22386
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cJma+HPrXvLmmw3OSfCTQTcz0c0S+haZcrAYoewDKQOq95q4KlLvXwXzfJ6u6sjCWUl7wf+FlxvLr46+QBu+Bg==