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
- 9ab1520ff6676ceca1b10d6e4f039cca1dc44577f1f169e563546ee93325ca7f
- request
- a57bedd073ae045d103f37ef1d2fa316e3edef41868916a229fb64023392b126
- transaction
- 2cc24d93239228220e599e798598f739b0500245ca5944e1e6dc686ceb775db4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56633
the chainentry 56633
- sealed to the entry before
- e2d9be55ef243f97fe31e083db9aab504e10ceefff4c719152661a726ff8df50
- this leaf
- 7e8e5a10bcdd0231726b3795d61d6dc5f2f067b2f21192835431906eed7761b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kLGMwAJIrSYIjxhqU9i4905hBm7tQtYM6okHxit2V8YfjiUxEjtbhFniITZ5C4PEIJ8iTK9QiDnR/a2ZU/DsAg==