2.85.89 ProntoPayments v2

Owned by Posimente
May 23, 2023
2 min read

Release Date: 17/2/2023

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

 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

  • Manage Payment Source - Searchable Person Account. To use this feature. This is the link, to how to use and what are the risk. (find link below)

    https://alphasys.atlassian.net/wiki/spaces/PRONTOPAYMENTS/pages/1746468931/Upgrade+to+Patch+2.85.86

  • ProntoPayments Settings custom setting. The API name ASPHPP__GP_IsSched__c field by renaming the field label as Unrequire BSB

  • ProntoPayments Settings(Ui) → Settings → Basic. In the Enabled features section, a new toggle has been added for Unrequire BSB below the Australian Bank Account Validation toggle button

  • Manage Payment Source page
    If the Record Type is Bank Account, the BSB field is displayed but NOT required if the ProntoPayments Settings custom setting is TRUE, otherwise it is displayed and required.

    • When creating/updating an Opportunity record,

      • If the Payment Type field is Bank/Direct Debit,

        • If the Unrequire BSB field from ProntoPayments Settings custom setting is TRUE and if the Payment Source field is populated with a Payment Source record where Record Type is Bank Account,

          • The Opportunity record will be saved successfully

          • Display an error message when saving the record: Payment Source must be a non- tokenised Bank

        • If the Unrequire BSB (ASPHPP__GP_IsSched__c) field from ProntoPayments Settings custom setting is FALSE,

          • If the Payment Source field is populated with a Payment Source record where Record Type is Bank Account and with complete Bank Account details,

o The Opportunity record will be saved successfully.

  • If the Payment Source field is populated with a Payment Source record where Record Type is Bank Account and with uncomplete Bank Account details,

    • Display an error message when saving the record: Payment Source must be a non-tokenised Bank with complete Bank Account details

  • If the Payment Source field is populated with a Payment Source record where Record Type is NOT Bank Account,

    • Display an error message when saving the record: Payment Source must be a non-tokenised Bank with complete Bank Account details If the Gateway field is NOT Payment File,

      • If the Payment Type is Bank/Direct Debit,

  • If the gateway supports tokenised payment,

    • Existing functionality will be followed

  • If the gateway supports non-tokenised payment,

    • If the Payment Source field is populated with a Payment Source record where Record Type is Bank Account and with complete Bank Account details,

      • The Opportunity record should be saved successfully

    • If the Payment Source field is populated with a Payment Source record where Record Type is Bank Account and with uncomplete Bank Account details,

      • Display an error message when saving the record: Payment Source must be a non-tokenised Bank with complete Bank Account details