Release Date: 11/4/2023
URL: /packaging/installPackage.apexp?p0=04t0I0000016FlT
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
When upgrading to version 2.71 or higher, make sure to re-save existing gateway records to have the password field encrypted.
Enhancement
Payment Source Creation
When deactivating an active non-tokenised/tokenised Credit Card/Direct Debit Payment Source record,
The Payment Source record will be deactivated successfully except if there are still pending Opportunity records linked to the Payment Source record
When activating a deactivated non-tokenised/tokenised Credit Card/Direct Debit Payment Source record,
The validation related to the Credit Card/Direct Debit will be executed
The Payment Source record will be activated successfully
Reusable Component with BPoint gateway
If the payment processing is failed due to no response from the fraud screening process,
A Payment Transaction record will be created where:
Payment Status = Failed
Transaction Message = “No response from Fraud Provider; or could not contact Fraud Provider. Transaction Rejected.”
Customer Id = EMPTY