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
- ccef5d496fcf662505db45edf6a0cc1bfab9f77ccf36bf1be0ae13766ed91170
- request
- 7ce710962f905bd60b2ab012dbacf52a210ed8fdba1738b3e228364fbb2836f7
- transaction
- 6baa770e649a83b1dd572bc9a28764e463817dbb038df157d32edd97c428813bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60548
the chainentry 60548
- sealed to the entry before
- feb0fe3e23fa6f58b7e9df257be722134bc512825b7172dc8fc53b9786ed0ab7
- this leaf
- 4fc50096139b6c89fe7b14de3dcdf8a857486c890127c1874b3e3460c3774f8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HQDERyh9aTTYq8BT/emqC74jY55IPxgi6nt0wWlVbREzYXyuzNFQb74ozDaEQCXGBYbD0rPKOhRr8tm0ncqyAQ==