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
- a94d760c822b7cfd5beb38805f34d80064bb4917eb061229febf62a4aa9a5843
- request
- e5486fadbd34a7a0949ab8995151d040ad7fefb72d2a074f3fcff2026b405748
- transaction
- 33146bf409aad656ad1a4e9723cfb33d118cfdb44f33ee138fc8046dea229191computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62401
the chainentry 62401
- sealed to the entry before
- b4115aec20facaeaef655480e16beeeb9b637a0818c5951a0bcb6cac2fece616
- this leaf
- 4ee261148c014e8e1a8bd845969ee42aa691f7875e09f2545e8ecefd93ba76d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aiZnojuVTtO7V1MX/MQQfQ1DbG1oYVzUoSoXQSN4zw57E2K0lrzVidhEV5Mt/HZPjEcRMQGFZhJ4yqdGzWLNBw==