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
- 56b1eed6dfd41bbf2781af7a8115ffd777f11c0df0e57cf94597af269cec1cef
- request
- 8a8c2b62ce9ad42692802ebf3f9781b68b3e8606eead04b3609f4d905566fdde
- transaction
- e2c52ab9592e3e7a93ce9fd15fbef518d9c9f3210253b31a9a3d8af687218b03computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52016
the chainentry 52016
- sealed to the entry before
- 2702b750ed9e91c95552d78dc3633bdeb00c6caff2ee0a0c9ffb0f89d09a42d3
- this leaf
- e842267599caa13b7f6f959bcfcf336b2dc450f68bba9cf54b18af724d065210
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RSR1jgmUGBP9syD4IXEN5hEe8/XYgMQ6g7crOPfOXMQfEZrxxArvCqu5NQ8/zsogaQlkvHU8Pa7DXZKCGBsZBA==