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



  • Production Server

    For processing live transactions

  • Test Server

    For development

Most Commonly Referred to Articles

ACH WEB Introduction

PayJunction's /plaid API offers a way for integrators to create ACH WEB transactions that are compliant with industry standards for e-commerce solutions.

ACH transactions through PPD and CCD require the merchant to obtain explicit authorization from the customer via a signed form each time they charge the customer's bank account. By using PayJunction's /plaid API, this step is eliminated because the customer directly authorized their account. Additionally, this API offers other benefits, such as verifying that the customer has sufficient funds available to cover the transaction, which can help reduce the number of transaction rejections.

General Overview 

To process an ACH WEB transaction using a plaidAccessToken, the general workflow is as follows:

  1. Include the Plaid Javascript SDK in your web application:
    <script src=""></script>
  2. Request a plaidLinkToken using POST /plaid/link/token/create.
  3. Submit the plaidLinkToken to the Plaid Javascript SDK:
    token: plaidLinkToken,
    onSuccess: async (plaidPublicToken) => {

    The Plaid Link process takes control here and facilitates the customer authorizing with their bank to grant access to their account

    Once the user completes the process, a temporary plaidPublicToken is returned via the onSuccess callback as seen in the code sample above.

  4. Submit the temporary plaidPublicToken using POST /plaid/item/public_token/exchange to create a non-expiring plaidAccessToken. Conceptually, the plaidAccessToken is similar to a PayJunction vaultId, and references the specific account the user provided access to.

  5. Submit the plaidAccessToken using POST /transactions whenever an ACH WEB transaction needs to be processed.