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
- 70f3003b10fd2bfe12517e038a4721bb9e239495663628cbcb8329a22b2893e9
- request
- 85120489b2ed11d5cc6ae0c2cc35a248d6313d974f0b5eb7a7728a52cfcc8e37
- transaction
- af6b9263cba33644154ed5840404dee50d5085a4750fd5a247015d42a979e386computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29526
the chainentry 29526
- sealed to the entry before
- b87fff752a34d2eb898abd03da7e9c57ce4f2e4b0fc85b3bf38033f13b48b9a3
- this leaf
- 5066fbf0b9fc9044c8391a005533fe8b27100558ba0d4afc42055c67d9b8d050
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O7gO9QqIXXoacEwEEQnT6rFUKTY/hy8NirfTefcNMJcsIHg7L2F6m70S47D/m5x1Vr67Fjy4AFx5XPrzudJQBw==