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
- 761f38aacb739dce6418b06db84d1c1f7c0de0aa9552e1ca16803e2527f11ce4
- request
- 7c5904b218b996dded706f879323a3f9b507678ec543334fbbcb7e342165e821
- transaction
- 727d61ca92a215f6d51695518811276065ce9ad17eb65d9ffba860e4c4765bcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40144
the chainentry 40144
- sealed to the entry before
- 34d2ecaa855e98d0207c12f87992a219d584d9cf4ecc099d5d6e1430c3d8a98f
- this leaf
- 4b298ccaffe17e4a14bcc2932a21a96adcd60a1af4946d1d53578bf873c6938d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KK0UDACdpN4l03aEOMZZuFlhvSaSUNS6tRO/T2LvXs/+MR7y7SFAawl7WavQnpiWKvhg+VAGuqpEP9TbaZTGBA==