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
- 6c1f469e1ff9441ac3a0da826f0f0a3c7dcd885a9db9c12d1888698369b4cd15
- request
- 0ea011662a2dbc003bc48daac3dcc0ddb815991053cc1ee82bdbf33cd0fff531
- transaction
- 60f797f37bb9416e7b083bb98c08bb3832edc307876d1df4d2b035d5e4a9e0f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22128
the chainentry 22128
- sealed to the entry before
- ce29fe3806d3fa5789faceafe145574c9e7edf92317e451d11e26f0f2afe7812
- this leaf
- d9b07b14c61782eb7792f0ec852d7ce3de2bd51d2883affab63fee7050dc1e9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w7KxS57ToWHgJImHIWKLYeQJPOlvuR99Z7agE6kqABff8Dcu4aukOI8bDxne0Mpvu12aj/YIanY7V2sBc/EMAA==