- 200 Success
The request was understood and successfully processed.
- 204 No Content
The request was understood and successfully processed. The response contains no body most likely because the entity was deleted.
- 400 Bad Request
The request was rejected due to a validation error. Likely a required parameter is missing or the data being sent is invalid.
- 401 Unauthorized
Authentication error with either the API User Login, Password, or Application Key. Your credentials are invalid.
- 403 Forbidden
You are making a call to a resource you don’t have permission to access. This can result from bad data or limit enforcement.
- 404 Not Found
You are attempting to access an invalid resource and it cannot be found.
- 405 Method Not Allowed
The HTTP method you sent is not allowed for the URI. Example, doing a POST when a PUT is required.
- 406 Not Acceptable
The HTTP header has an invalid Accept parameter. Currently this API only supports JSON responses. You must set Accept: application/json
- 500 Server Error
PayJunction server error. Report this to PayJunction technical support.
Offer all the payment features your
customers want with a fast integration
that limits your PCI scope.
API Base URLs
For processing live transactions
Most Commonly Referred to Articles
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.
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*
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.
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.