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
- 7b564c80d0d05c12f57a1d37deb72df3e278236d52db4e2f008bfde14099d91c
- request
- 0a17635b3949edab365533c002c7008bca16b1bc5b1b8cfc009e1dc9504a8bef
- transaction
- ab10d4d1ceda88468b518674ed3de574ffa767e4d8eb1996092d0eb3fca56937computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65997
the chainentry 65997
- sealed to the entry before
- 6bcc6f9ab5d4daf8f478c6bbe8e6e2ae7c1d32539b7b341ecfe41962fbc5539a
- this leaf
- 6a9efcf3f1b1aeeff28010516881104426a75a98096844d67d3b2a881e56fc38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JhVXPMzbBnPlx73jpp+4cJyx0YebLnl09c9fM9N48aFZHrX7nYJ9bRFZnDkhnPbLjiZl3y5XkuC9xTa9Yst7BQ==