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
- e12985c091eff4381d2073c36c8a749ac6ee8df96b90b8027db6c1a905ebd55a
- request
- 607c9bb852ad9a0d7dc68d709d2ecd53f9e15b3ddb5215809d4dce2ca8e0f989
- transaction
- 07370a13110f98660d0db99c5dbc323b503b14cf155109d9821a7bc47776903acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51891
the chainentry 51891
- sealed to the entry before
- 0bd245860305368b363cfeaeb38ca64287f24a66c3c3794023423e5ad8e5fc61
- this leaf
- 94e338a52c66735db9a16f430b918df25aaa4004cc782215b7ef23e39b79719a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tuLVitu5WUm2nAZbHK0Wf41TCN+m5bpUzLr80I8zBLSogfpV011Drfc0/MXgm2I112LLb49BQhxVmoaqMDE0AA==