Release Date: 2/6/2023
URL: /packaging/installPackage.apexp?p0=04t0I0000016Fsj
Important Reminder
This version has a known issue with the following description:
Payment Source having a not 'Active' tag when created via Manage Payment Source in Opportunity.
The newly created Payment Source will not automatically populate the Payment Source field in Opportunity.
Credit Card number is fully shown in the Credit Card Number fields having an API name ASPHPP__token_Card_Number__c and ASPHPP__Card_Number_c.
This issue affects 2.85.91 to 2.85.102.
Version 2.85.103 (click here) resolves this issue. If you prefer not to upgrade at this time due to other factors, a workaround would be creating an automation that sets the Payment Source to active. This ensures that the card information is encrypted.
Upgrade Risks
Make sure WIT components are passing the encrypted session ID and make sure to re-save existing gateway records to have the password field encrypted.
Enhancement
Process Payment via Batch or Button
If the gateway is Securepay,
Set timeout to 120,000 milliseconds for API callout request
If a “CalloutException” exception error type is hit in Salesforce,
The following fields of the Payment Transaction record will be populated:
Payment Result Code = exception error type (e.g., System.CalloutException)
Transaction Message = exception error message (e.g., Read timed out)
Payment Status = Pending
On the ASPP Log record of the Opportunity record, populate values to the following fields:
Lock Record = TRUE
Message = exception error type and message (e.g., System.CalloutException: Read timed out)
Reusable Component
If a “CalloutException” exception error type is hit in Salesforce,
A Payment Transaction record will still be created
Reusable Component will return:
Response Message = exception error message (e.g., Read timed out)
Error Code = exception error type (e.g., System.CalloutException)
Limit (stored in error code JSON string) = TRUE
Status = Pending
Payment Transaction = created Payment Transaction record
Bug Fix