In order to connect and send requests to the PayJunction API, you will need the following:
TLS 1.2 will be the minimum PCI compliant protocol in July 2018 at which time PayJunction will make it a requirement to send requests to our production servers. In order to encourage developers to update their software now, PayJunction requires it for the PayJunctionLabs.com sandbox domain.
Application keys are used by PayJunction to identify which service or application is sending traffic to our API so we can better work with developers to fix issues and notify them of important updates. They are not tied to any particular merchant account set up with PayJunction and should be the same for all instances of a specific service or software.
For example, if I have an application which connects to PayJunction used by a thousand different merchants, the application key should be the same for each merchant using my application. If I had two separate applications to provide different services, I would obtain a second application key from PayJunction.
When your request has been processed, you will be provided with a set of keys, one which will work on our sandbox domain, payjunctionlabs.com, and the other for the production domain, payjunction.com.
TIP: PayJunction support staff review each request for application keys. This is usually completed within 1-2 business days. To help prevent delays in having your application approved make sure to provide legitimate contact info.
The API Login and Password
PayJunction uses the API login and password in order to authenticate access to run transactions and to determine which PayJunction account to process the transactions through. These credentials must be sent to PayJunction using HTTP Basic Authentication.
Authorization: Basic base64("apiLogin:apiPassword")
More information regarding Basic Authentication can be found here.