Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Release Date: 1/5/2023

URL: /packaging/installPackage.apexp?p0=04t0I0000016FsP

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 BPoint,

    • If the response code is 999 and the Hard Bounce Codes fields has 999 value in the Gateway record. The Stage Name of the Opportunity will update base on the value of the Gateway’s Stage for Failure when hard failure. 

 Bug Fix

Create Payment Source using workbench 

  • When the data is Amex Card, then when saving the record, the record is not successful save. This package version is fixed. 

  • No labels