Offer all the payment features your
customers want with a fast integration
that limits your PCI scope.
For processing live transactions
For development
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.
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.
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.
WEBHOOK SUBSCRIPTIONS ARE LIMITED TO 5 PER PJMID. But a single Webhook can simultaneous track multiple requestI IDs.
For more information on PayJunction account structures, see the PayJunction Account Structures guide.
Deletes a webhook.
On successful delete, returns HTTP Response 204 No Content.