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
- 5a510b3fca1a37aeeaf3bdc6db28c4e2f368d3cad7603db584453c8e5359692f
- request
- 4f2279c0ee81fcde40d55793ae83afe8b8b2b82a94967b9c157423fa50360f85
- transaction
- ed3583bfe6cfcaeb9754ca6fb7599861c6e683fb8ecc6c8ab383e9aeb89345efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25238
the chainentry 25238
- sealed to the entry before
- ab3b5c81c8a859f24064bced2b4504654e485e3fa9f64c23c0c33b21332e30f2
- this leaf
- 8b06654dca4c1a542497dfe63245883adcbcca41dd1e3fe8929a96311bc1f178
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kUcRPHrRQWaGb3rHGOOLaCNqML92pwF5CFCj8arTikSF923iX4JWOMWpCGcT9LSaKA7YtA5CPVOznjQ8RKrcBw==