I'm very confused by both the configuration of this module and the error messages it is giving me when I try to use a test account. I've looked over the source code and examined Linkpoint's PHP class, and I've even talked to tech support. Unfortunately, I can't get past this error (if I specify the WSstore_id.pem file as recommended generated by the "Web Service" download button):
unable to set private key file: '/Users/rszrama/htdocs/linkpoint/sites/default/files/WS1909924218._.1.pem' type PEM
The file: /Users/rszrama/htdocs/linkpoint/sites/default/files/WS1909924218._.1.pem exists: check your pass phrase or verify that you have selected the right "transaction server" for your certificate (PEM file).
Or this error (if I specify the store_id.pem as generated by the "API" download button):
Payment failed for order 3: Credit card declined for $1.00 with error: SGS-020006: Please contact merchant services.
The thing is, when I was talking to tech support, I was told that it was the latter .pem that I needed, not the one directed by the description text on the form.
So... what in the world is going on here? Has anyone actually used this module successfully to get to the test gateway? Is there something faulty in my development environment I should be looking to?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 981378.uc_linkpoint_api.pem_file.patch | 3.12 KB | rszrama |
| #2 | 981378.uc_linkpoint_api.pem_file.patch | 0 bytes | rszrama |
Comments
Comment #1
rszrama commentedOk, so my problem was there was an apostrophe in the last name of the contact info on the account. Pretty retarded that they don't sanitize the data before generating keys. However, I did confirm that the instructions on the module installation are wrong - I don't even know how people have been using this. : ?
Instead of using the WS[store_id]._.1.pem file, you should just be referencing the [store_id].pem file. This is downloaded by using the API download button in the download center. The web service key is only used for the SOAP web service and requires a lot of additional setup. The description text should be updated to point to the proper button.
It would be nice to get some installation instructions on the module's project page, too.
Comment #2
rszrama commentedPerhaps the attached patch will suffice? I've updated the README.txt as well.
I still think quick Installation instructions on the project page would be good, too.
Comment #3
rszrama commentedJumped the gun on the patch upload. Here it is.
Comment #4
jrust commentedThanks, applied in CVS and I'll update the page w/ instructions.