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
- 7c8ee6805b56397432496663c37197e438b7e26576319917b35431b6bb3cf725
- request
- e26e3b666e2a92160a82bc218c4c8d4a17110ac6dee047302c19ebfd2308e4f6
- transaction
- 8e25f1a06995168a90d8f2ed63ff42dc7f34fd213d6352b2e5e763c815be789bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30772
the chainentry 30772
- sealed to the entry before
- 4b81db83d4d3ca6bda9a777ed4aa9266a4f1327be9671f255130c7a1060f7d08
- this leaf
- a7f64a4cd77c42bb865c461d4ea9dff4277c297032c0674cac5c5f707f714ab6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ONNj+998pXbG0hFjHir+LME/75NbRUtCgEa7jO1d9ClRNVbNaX2xVv+1tvK0qiqnlqkm11X8p5Z3K/2hMfGmBA==