About CPX

Commercial Payment Exchange is a seamless, end-to-end solution which can be used by institutions offering automated account payables solutions to their customers. It provides these institutions the capability to process payments to different suppliers using different instruments through a standard file format. It offers discounts, rebates, and incentives to the customers through supplier activation. It also supports an interactive portal that provides complete control and full visibility of payment status through easy, yet robust, reports.

Enhancement

1. CPX to allow users to add Buyer details in CPX to onboard buyer on Visa (CPXBIZ-810)

CPX has now been enhanced to allow users to be able to add buyer details in CPX which would automatically onboard the buyer in Visa (VPA).
Earlier users had to manually onboard a buyer in TSYS followed by onboarding in Visa (VPA) and then configuring the buyer details in CPX.

Implementation

• CPX has been enhanced to add buyer details in CPX which would onboard a buyer in Visa (VPA) directly.
• At the institution level, a new configuration has been added for Visa (VPA) as Implementation Type. The user can setup the value as Pseudo accounts or TSYS Virtual accounts. This should be set as Pseudo account for the current buyers.

Image 1: : Implementation Type added as a new field under Card tab under Institution Settings for Visa (VPA).

• At the buyer level, for Pseudo account configuration, the user can add the Buyer template ID and the Buyer ID. The buyer Id should be existing on TSYS and the Buyer template ID should be existing on Visa (VPA).

Image 2: Buyer Template Id added as a new field under Card tab under Buyer Settings for Visa (VPA).

• Once the user has added the details, the user can add the Funding account details. The funding account number, Credit limit and Expiration Date should be added and should already be configured on TSYS.

Image 3: Funding account Information needs to be added to setup Visa (VPA) at the buyer level.

• Once added, Funding account number cannot be edited, but Credit limit and expiration date can be changed and would be updated on Visa accordingly.
• Once buyer and Funding account configurations are setup. The user can add card management rules on CPX.
• The user can add single or multi use card rules and add user defined Proxy Pool Id. To setup the card management rules, users would also have to add Initial Order Count, Minimum Available Accounts, and Reorder Count.
• The Initial Order count refers to the Initial count of available accounts/cards in the proxy pool at the time of pool creation. The minimum available accounts refers to the minimum count of accounts/cards that should be available in the proxy pool at all times. The Reorder count refers to the count of accounts/cards that should be ordered once the pool reaches the minimum count level.

Image 4: New fields added for Card Management Rules for Visa (VPA) for card under buyer settings

• The initial order count should always be greater than the Minimum available count.
• CPX would call the requisite APIs to create buyer, funding account and proxy pool on Visa (VPA).
• If there are any errors in creating buyer, Funding account or Proxy Pool on Visa, the relevant error messages would be shown in corresponding sections. The user can only process payments using Visa (VPA) if buyer, funding account and Proxy pool have been configured correctly.
• Internal admins can delete the Funding account details as well which would clear the funding account details but it would be mandatory to add funding account details to save the buyer. Deleting the funding account does not delete it on Visa, it only allows to delete the information from CPX.
• If the funding account is changed, the card management rules would become irrelevant since they are associated to the previously set up funding account and would have to be deleted manually and new card management rules would have to be added to be able to process payments.
• The user can delete card management rules/ proxy pools as well. This is only allowed if there are no existing active cards associated to that pool else deletion would not be allowed.

Impact

This would allow users to be able to setup Visa (VPA) on CPX and reduce manual overhead to setup the same on Visa.

Table 1: Impacted Screens

2. CPX to allow processing of ACH returns for UMB (CPXBIZ-901)(Hotfixed with Exeter City)

CPX has been enhanced to process ACH returns for UMB.

Earlier CPX was receiving returns for transactions but it has been tested for different NACHA ids as well.

Implementation –

• CPX has been enhanced to process returns from ach.com for UMB and update the ACH transactions as returned.
• CPX would be receiving ACH returns as usual via ach.com and CPX would be consuming this information per NACHA ID and update the transaction on CPX as returned.

Impact

This would allow UMB to be able to get updated on returns on the ACH transactions.

3. CPX to support other as a billing method for ACH (CPXBIZ-900)(Hotfixed with Exeter city)

CPX has now been enhanced to support other as a billing method for ACH as a payment method.

Earlier CPX supported Good Funds and Pre-Fund as a billing method for ACH.

Implementation –

• CPX has been enhanced to support other as a billing method for ACH payment method.
• If other has been set as the billing method for ACH, CPX will not be creating any debits for the ACH transactions, only credits will be processed for these transactions and the billing will have to be done manually.

Image 5: Other introduced as a billing method for ACH under buyer underwriting.

• Additionally any NACHA files being generated will only have credits and will be unbalanced NACHA files for such ACH transactions.

Impact:

This would allow CPX users(mainly UMB) to be able to user other as a billing method for ACH and get billing for the transactions separately as well as receive unbalanced NACHA files as requested.

Table 2: Impacted Screens

4. CPX to introduce custom roles for AMC (CPXBIZ-922) (Released with Exeter City)

CPX has now been enhanced to allow custom roles for AMC Institution

Earlier CPX allowed standard roles for all users and no custom roles were available.

Implementation –

• CPX has been enhanced to allow AMC to be able to add users with custom roles.
• Three custom roles have been setup as AMC System Admin, AMC Property Accountant and AMC Accounting supervisor.
• The roles are similar to Institution admin with certain additional restrictions. The Property Accountant and Accounting supervisor have the same set of privileges.
• Only AMC institution can have access to these roles. Users can only be assigned AMC specific roles by Internal admin users or users associated to AMC institution already.

Image 6: New Custom Roles introduced for AMC under Users tab.

• Any privileges not mentioned will automatically be provided to the custom role by default if a similar role in CPX has those privileges.

Impact

This would allow AMC to get onboarded while allowing their users to have custom roles thereby helping CPX generate revenue.

5. CPX to consume Auth and Settlement information for Visa VPA (CPXBIZ-810) (Hotfixed)

CPX has now been enhanced to consume auth and settlement information for Visa VPA.
Earlier CPX was able to create transactions on Visa VPA but CPX was not able to receive any auth or settlement updates leading to transactions not getting updated as per auth and settlements activity.

Implementation –

• CPX has been enhanced to receive auth and settlement data as Push notifications from Visa VPA.
• This will allow CPX to consume any auth or settlement activities from Visa and update the transactions as per the activity allowing users to get updated on auth and settlements against the payments.
• On receiving an auth or settlement notification CPX would update the auth or settlement history against the payment and would update the status of the transaction as well.

Impact

This would allow users to get updated on auth and settlements against the payments.

6. CPX to generate custom Billing report for UMB (CPXBIZ-852) (Hotfixed)

CPX has now been enhanced to create a custom billing report for UMB buyers.
Earlier CPX was creating a custom billing report for Heartland only.

Implementation –

• CPX has been enhanced to create a custom billing report for UMB as well.
• CPX will be creating the report with different billing elements including Check fees as received from Smart Payables and count of various transactions.
• Additionally any elements that have a 0 count will not be included in the report and the report would only include accounts which have ACH or check set as default. Additionally CPX would also fee associated with check payments in the report once the check has moved to Sent status.

Impact

This would allow UMB to receive Billing report as per different elements for its buyers.

Bug Fixes

1. Fixed issue with CPX not being able to receive authorization information from Visa (CPXBIZ-810) (Hotfix)

It was noted that CPX was not being able to sync authorization data from Visa (VPA) due to incorrect date format. Additionally CPX was not being able to parse authorizations in the correct order for Visa (VPA) payments. The transaction has an auth decline followed by authorization but CPX parsed the authorization followed by auth decline leading to the payment being updated to Auth declined.
This issue has now been resolved and CPX is able to consume auth and settlement data from Visa to update status of transaction and CPX will parse the authorizations in the correct status.

2. Fixed issue with users not being able to view card details in disposition files (CPXBIZ-925) (Hotfixed with Exeter City)

It was noted that users were not being able to view card number and CVV in disposition files. This was due to recent changes in file importer where CPX started passing only last 4 digits of the card number which were being sent in the disposition file instead of the full card details.
This issue has now been resolved and users will not be able to view the card details in the disposition files.

3. Fixed issue with exposure limits not getting updated for users as per the setting (CPXBIZ-921) (Hotfixed with Exeter City)

It was noted that when exposure limit was set for payment methods for users, the limit was not getting refreshed as per the time duration set leading to files getting stuck for approval due to the exposure limit getting breached falsely.
This issue has now been resolved and the exposure limit for different payment methods would get refreshed as per the time duration.

4. Fixed issue with file staying in Pending External approval even if all payments are failed (CPX-5819)

It was noted that when External Dual Approval was set up for a buyer but the external status of the supplier was inactive, all payments under the file would be failed but the file still remained in Pending External Approval status.
This issue has now been resolved and if all payments under a file fail before the file is held for approvals, the file would be marked as failed as well.

5. Fixed issue with Merchant details not getting populated for Lodged transactions for Payments/PIF report (CPXBIZ-572)

It was noted that merchant details were not getting populated for Lodged transactions for Payments/PIF report .
This issue has now been resolved and merchant details will be populated for lodged transactions for DXC and Galileo as well as VCN transactions for Visa (VPA) as well in the Payments/PIF report.