New LinkPoint API?

I received 2 voicemail messages from LinkPoint stating that I need to update my API software soon in order to process credit cards using my CardService International LinkPoint account.

Is there something specific I need to change within OptiGold or have you already prepared for the new API change that LinkPoint is about to implement?

Please advise.

 

where will i be able to download & install this update?

 

I'm the one who will be upgrading OptiGold's CCAuthorize plugin to the new LinkPoint API. I Promise everyone it will get done, and I've already spent some time looking into the new stuff. If anyone knows the exact date they will be shutting down the old API, please post it here. And everyone dependent on LinkPoint with OptiGold, please subscribe to this thread with email notifications since I or Shawn will post news here.

Regarding changes with the new API, I don't think anything will have to change in OptiGold, you'll only need the new CCAuthorize plugin. However, the .pem key file you received when you signed on with LinkPoint will need to be reprocessed, and I'm not sure if this time around I'll be able to do that automatically in the plugin. If I can't, I'll provide do-it-yourself instructions for the unix crowd, and a web form you can use to submit your .pem file to and get back the individual components required.

-wayne

 

here's the message from LinkPoint regarding the old API cutoff.

Conversion Period If you are currently using an older version of the API, you will need to upgrade to the latest version between January 1, 2005 and February 28, 2005. It will be necessary to complete your conversion prior to February 28th, 2005 to avoid a disruption of service.
​

-wayne

 

I was just on the phone with surepay.com which assures me that I have to cut over to linkpoint or yourpay processing by Jan. 31.

 

Are we going to have time to test this before the cut off? Whats the deal with not having an update until the very last minute? We rely heavily on surepay and OG for all of my receivables and this is absolutely not comforting nor should it be acceptable. Whats the status form Digitalpoint??????

 

LinkPoint API Update is finished. If there are any SurePay customers out there, this will apply to you too. I'll coordinate with DigitalPoint to get the update tested in OptiGold and released, hopefully yet today.

A word of warning, the .pem key file LinkPoint sends you will need to be converted to a new format. There's a CGI that you'll be directed to for the conversion.

-wayne

 

Sorry Delrey for it coming down to the last minute. It's my fault, not DigitalPoint's. Poor shawn had to field all those calls from the anxious LinkPoint customers.

 

Where do we get this?

"There's a CGI that you'll be directed to for the conversion."

 

I need this too, my linkpoint stopped working with Optigold today.

 

OK Gang,
Here are a few of the CCAuthorize plug-in release notes related to updating your .pem files, along with a URL for handling the conversion.

the URL for converting your file is here:
http://www.acmetech.com/products/ccauthorize/pem.php

Notes follow:

== Digital Certificate [pem] File ==
You MUST convert your .pem file to a new format. If you were already using LinkPoint with CCAuthorize you'll find this file in the FileMaker Java Extensions folder with FileMaker's directory. To generate the necessary .p12 file from your .pem file, visit http://www.acmetech.com/products/ccauthorize/pem.php. After
generating your .p12 file, place it in the FileMaker Java Extensions folder.

IMPORTANT: the password used to secure the .p12 file must be sent to the CCAuthorize plugin as the PASSWORD parameter, DO NOT USE YOUR
STORE PASSWORD (i.e., the one you use to log into the virtual terminal at secure.linkpt.net)!!

You can update your key file yourself if you have openssl installed. Use the following cmd:

The .p12 file MUST be placed in the "FileMaker Java Extensions" folder as "<user_id>.p12".

 

I converted my .pem file to .p12 format and saved it in the /FileMaker Java Extensions directory.

I also right clicked and installed the certificate.

I'm still getting the error:

Unable to connect to SSL Server.

 

Confirm that you have at least, version 3.4.6 of the CCAuthorize plug-in installed. Somewhere towards the beginning of this thread Shawn wrote regarding where this info can be found.
-wayne

 

I am running the following:

Optigold 3.3.7
CCAuthorize v2.8.1

What port is Linkpoint now using? I heard it changed. I think I need to open access to this port on my firewall.

 

You'll definitely have to upgrade the CCAuthorize plug-in. It appears LinkPoint makes outgoing connections on port 1129.
-wayne

 

I forgot to do a workstation install which I just did and am now running the newest CCAuthorize.

I now get the error message:

java.lang.Exception: IO Error, possibly a problem with config (.p12) file: failed to decrypt safe contents entry

The password I used at http://www.acmetech.com/products/ccauthorize/pem.php is different than the password i use to login to my Linkpoint account. But it does say at http://www.acmetech.com/products/ccauthorize/pem.php, "You will have to supply this same password to CCAuthorize when processing transactions."

Where exactly do I have to enter the password for the certificate so i can process payments?

 

Davet,
There may be other configuration within OptiGold required, but whatever password you used for the pem.php cgi to generate your .p12 you'll need to use in the CCauthorize/billing setup screen of OG. Here's a note from another OG user who was writing to say how he got it working without upgrading to OG 3.3.7, but it may have useful information for you:

NOTE FOR OG USERS:
Shawn and Wayne,
Thanks for your help on getting the Linkpoint API/CCAuthorize interface working. I thought I would document what TCQ Internet had to do to get it working properly without upgrading to OptiGold 3.3.7. The new interface works fine.

Ciao,
Gary


1) Run the <storenumber>.pem file through the following URL and save the .p12 file to the FileMaker Java Extensions folder

http://www.acmetech.com/products/ccauthorize/pem.php

Alternatively, run it through "openssl pkcs12 -export -in <storenumber>.pem -out <storenumber>.p12" and be sure the export password matches the Linkpoint password. Save the .p12 file in the FileMaker Java Extensions folder.

[Next item: NOT NECESSARY, HAS NO EFFECT -wkw]
2) On the Billing Preferences screen, change Hub Port Number from 1139 to 1129. 1139 is the old API port, while 1129 is the new API port. The new API will not work with port 1139.

3) On the Billing Preferences screen, enter the Linkpoint store number in the Authorization Customer ID field. This field was apparently not used by the old Linkpoint API, and was set to a default value of 111.

 

Thanks, we finally got the credit card billing working again.