Therefore, developers that are using platforms that do not support TLS 1.2 or higher will not be able to establish connections with the PayJunction API. If a merchant processes through two different PJMIDs your service will have to subscribe to webhook events for both accounts to receive all data.īeginning on June 1st, 2018, in accordance with PCI security guidelines, PayJunction requires the use of TLS 1.2 while establishing connections to our API. Webhooks, like all parts of the API, are tied to the PJMID for an account in PayJunction. Webhooks can be subscribed to via the PayJunction REST API. Keyed, Swiped and Recharged (Instant) Transactions: these types of transactions work in a traditional, synchronous manner: an HTTP request is sent to the PayJunction API and a success or fail response is immediately returned. All transactions that are processed via the test environment are for testing purposes only and no money will be collected. Additionally, you will be able to login to the test account in order to view all test transactions. The following information will allow you to process transactions via the PayJunction test account (i.e. In order to connect and send requests to the PayJunction API, you will need the following: A PayJunction Application Key, An API Login and Password, TLS 1.2 Support* Requirements for Connecting to the PayJunction API.The Smart Terminal will automatically determine if the customer needs to insert the chip card, swipe the card, enter a PIN or collect a signature. Initiate a transaction on the Smart Terminal. If you have uploaded ACH/Card data it can be re-billed via a Vault ID.

You can re-bill via a previous Transaction ID.

You can also re-bill via a Schedule ID from a previously created recurring schedule. Process an ACH (Electronic Check) transaction.

.net test tls 1.2