PAYMENTS
SIMPLIFIED

Offer all the payment features your
customers want with a fast integration
that limits your PCI scope.

API Base URLs

Production Server

For processing live transactions

https://api.payjunction.com
Test Server

For development

https://api.payjunctionlabs.com

Most Commonly Referred to Articles

POST/transactions

Process an ACH (Electronic Check) transaction. Process a keyed credit card transaction. Process a tokenized transaction. You can also re-bill via a Schedule ID from a previously created recurring schedule. You can re-bill via a previous Transaction ID. If you have uploaded ACH/Card data it can be re-billed via a Vault ID.
POST/ST/request-payment

Initiate a transaction on the Smart Terminal. 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.
Requirements for Connecting to the PayJunction API

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*
Development Sandbox

The following information will allow you to process transactions via the PayJunction test account (i.e. sandbox). Additionally, you will be able to login to the test account in order to view all test transactions. All transactions that are processed via the test environment are for testing purposes only and no money will be collected.
Transaction Processing Workflow

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.
Available Webhooks

Webhooks can be subscribed to via the PayJunction REST API. Webhooks, like all parts of the API, are tied to the PJMID for an account in PayJunction. If a merchant processes through two different PJMIDs your service will have to subscribe to webhook events for both accounts to receive all data.

Level 3 Data

Certain corporate, business, and purchasing cards used in B2B and B2G transactions are eligible for lower interchange rates if the transaction includes Level 3 data.

Providing Level 3 data does not guarantee that the transaction will qualify for Level 3 interchange rates. Qualification depends on multiple factors such as card type and the quality of the data provided with the transaction. Merchants are responsible for any fees that may occur when processing transactions with Level 3 data.

For more information about the benefits of Level 3 processing, see: https://blog.payjunction.com/level-3-credit-card-processing

Prerequisites

Level 2 data is a prerequisite to qualify for Level 3 interchange rates.
Level 3 processing must be enabled for the account. Submit a request here: https://developer.payjunction.com/hc/en-us/requests/new?ticket_form_id=152047

PAYMENTS SIMPLIFIED

API Base URLs

Production Server

Test Server

Most Commonly Referred to Articles

POST/transactions

POST/ST/request-payment

Requirements for Connecting to the PayJunction API

Development Sandbox

Transaction Processing Workflow

Available Webhooks

Our integration team is ready to speak with you.

Level 3 Data

Prerequisites

PAYMENTS
SIMPLIFIED

Our integration team is ready to
speak with you.