Equifax PayNet Update from SOAP/XML to REST/JSON - September 30, 2026

Equifax PayNet Update from SOAP/XML to REST/JSON - September 30, 2026

PayNet Integration Update - ASPIRE 5.20.73 and later

Overview

Effective September 30, 2026, Equifax (owners of PayNet) will officially move from a SOAP/XML-based integration to a REST/JSON-based integration. This means that ASPIRE’s PayNet Integration (ASPIRE version 5.20.72 and earlier) will no longer work starting September 30, 2026.

*Note that the current integration will not be affected and will continue to work up until that date. 

In preparation for this change, LTi has updated ASPIRE's PayNet integration to use REST/JSON starting with ASPIRE version 5.20.73 (and later).
It is important to note that as soon as you take the 5.20.73 build or later, the PayNet integration will not work without additional credentials to be provided by Equifax. It is strongly recommended to get these credentials (Member ID, Client ID, and Client Secret) prior to taking 5.20.73 or later into production. 

ASPIRE version 5.20.72 and earlier will continue to work until Equifax deprecates the SOAP/XML-based integration on September 30, 2026.

Administration of Credentials

As part of the transition to REST/JSON, additional credentials are required. The following is a summary of the required credentials:
  1. Customer ID.
    1. Provided by Equifax.
    2. If you are currently using ASPIRE's PayNet integration, this value will not change. This value is used in the JSON 'wrapped' XML request.
  1. Password.
    1. Provided by Equifax. 
    2. If you are currently using ASPIRE's PayNet integration, this value will not change. This value is used in the JSON 'wrapped' XML request.
  1. Client ID.
    1. Provided by Equifax (using their developer portal).
    2. This value is used in the JSON 'wrapper' for authentication.
    3. Customers will need to manage their own Equifax developer's account to manage their Client ID.
  1. Client Secret.
    1. Provided by Equifax (using their developer portal).
    2. This value is used in the JSON 'wrapper' for authentication.
    3. Customers will need to manage their own Equifax developer's account to manage their Client Secret.
  1. Member Number. 
    1. Provided by Equifax (using their developer portal).
    2. This value is used in the JSON 'wrapper' for authentication.
All relevant values can be entered into ASPIRE on the Administration menu - Credit Adjudication screen - PayNet section.


ASPIRE's PayNet Integration

At this time, there are no anticipated effects on the PayNet service within ASPIRE. Once the credentials are entered into ASPIRE as previously detailed, users will continue to be able to pull and view PayNet reports, including:
  1. Manually pulling PayNet reports
  2. Pulling PayNet reports using Contract Profiles
  3. Scoring PayNet data points view Scorecards. (Existing scorecards should not need to be edited)
  4. Viewing the full PayNet reports
  5. Viewing list of similars returned
  6. Configuring the Global Setting in ASPIRE that sets a threshold for list of similars

Setting up an Equifax Developer's Account

Customers will need to setup an Equifax Developer's account to maintain access to PayNet products in ASPIRE once the ASPIRE version 5.20.73 (or later) build is implemented or before September 30, 2026.  It is recommended to start this process as early as possible. The credentialling process does require an approval process on the Equifax side and the credentials provided are required to pull PayNet reports in ASPIRE version 5.20.73 and later. Getting these credentials early does not affect current builds using the PayNet integration in ASPIRE version 5.20.72 and earlier. Use the following steps to set up your Equifax Developer's Account. If you have issues setting up your Equifax Developer's account, reference their migration guide or contact usis_api_integration_support@equifax.com.
  1. Get your Member ID from your Equifax account manager.
  2. Go to https://developer.equifax.com/
  3. Create an account. Equifax suggests using group email to ensure continuity of service.
  4. On the Dashboard, Create a New Application.
    1. API Product = Commercial Credit Risk
    2. Create Application
    3. Copy Client ID and Client Secret to enter into ASPIRE
  5. Test PayNet pulls, Promote Application to Test.
    1. On the Dashboard, select Promote to Test under the application created.
    2. Equifax should reach out once your application is approved.
    3. Client ID and Client Secret should be available to copy.
    4. After approval from Equifax, you should be able to begin testing in ASPIRE test sites with PayNet integration in Test Mode (in ASPIRE, select the Test Mode checkbox on the Administration menu - Credit Adjudication screen - PayNet section).
  6. Promote application to production to pull production PayNet reports.
    1. On the Dashboard, select Go Live under the application created.
    2. Equifax should reach out once your application is approved.
    3. After approval from Equifax, you should be able to pull production PayNet reports within your production ASPIRE instance.
Equifax recommends refreshing your Client ID and Client Secret annually and sends email reminders to the email address associated with the Developer's account. Once the Client ID and Client Secret have been refreshed, the previous credentials will no longer work. To prevent disruption to the PayNet integration, it is recommended to refresh these credentials outside of working hours. 

FAQs

Is PayNet Canada affected by this change? 
No, PayNet Canada is not affected by this change at this time. The PayNet Canada integration is a separate integration and will continue to use the current integration architecture. While Equifax is continuing their internal architecture changes, at this time there is no planned change to the PayNet Canada integration.

Why do LTi's customers have to maintain an Equifax Developer's account? 
The Client ID and Client Secret are required by Equifax for the new REST/JSON architecture. LTi's Product Team decided the Client ID and Client Secret would be best managed by the customer so the customer can maintain consistent service and can control the timing of the annual refresh of credentials. 




    • Related Articles

    • Credit Report/Update Legal Name from Business Credit Report

      NOTE: As of October 1, 2025, ), the LiquidCredit integrations for both ASPRIE v4 and ASPIRE v5 will no longer be supported due to a change in architecture on the FICO side. Overview of testing results: The intent of this feature is to retrieve the ...

    • The Correct Document Type for Importing Microsoft Word document into ASPIRE for Doc Tagging

      While you may have heard that you need your Microsoft Word Document to exist as a .xml document, you probably noticed there are a few different options available as an "XML" document option when saving your Microsoft Word document to your computer ...

    • How to utilize the Global Equipment Update Module

      The Global Equipment Update Module launches from the Contract Explorer > Equipment screen, and creates an Excel spreadsheet of the existing equipment line-items and details. It allows a user to edit data and import it back into ASPIRE for the same ...

    • Update Jobstream Schedule

      In ASPIRE, go to Administration -> Jobstream Select the jobstream job that needs to be updated. In the Schedule section, update the schedule to the desired date/time. If the save icon does not activate, make a change to the Job Name field, then ...

    • Bulk Pool ID Update

      Bulk Pool ID Update There are various situations in which updating the Pool ID will allow you to process updates in Bulk through the Tasks > Bulk Contract Processing function in ASPIRE. The Pool ID can be used to select the contracts for update. ...