2024 Q2 Posi Giving Release Notes

Owned by Cherry Mae Descallar, created
Last updated: Jun 28, 2024
6 min read

ProntoPayments 2024 Q2 release notes are located in the ProntoPayments v2 section

Importance Notice

  • In ProntoGiving v2.207, using Purchase Transaction Type in Quick Donate requires the user to input Card CVV. When saving the record where the Stage field is automatically set to Pledged in Once-off Donation section, the Opportunity record is saved with the newly created Payment Source linked, and the Stage status is Pledged.

  • Newly created Payment Source will not save CVV/CVC/CNV as part of the PCI Compliance and we applied this in ProntoPayments version 2.85.113.

  • Processing via Process Payment button or Batch Payment Processing will return EWAY_CARDCVN Required response.

  • We advise using the Purchase Transaction Type for once-off payments in WIT.

ProntoGiving

2.207 (29/05/2024)

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

Required packages

ProntoPayments 2.85.119 or higher

Enhancements

  • eWay Transaction Type - Require/Unrequire CVV in Quick Donate

    • When donating via the Quick Donate (Standard) page → Enhanced RD is disabled,

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is NOT a required field

        • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

          • If the selected Payment Method = Credit Card,

            • The Card CVV field is a required field

      • When donating via the Quick Donate page → Enhanced RD is enabled,

        • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

          • If the selected Payment Method = Credit Card,

            • The Card CVV field is NOT a required field

        • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

          • If the selected Payment Method = Credit Card,

            • The Card CVV field is a required field

  • eWay Transaction Type - Require/Unrequire CVV in Replace Payment Source (PGIV)

    • When replacing the Payment Source of an Opportunity record via the Replace Payment Source page,

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is NOT a required field

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is a required field

    • When replacing the Payment Source of a Recurring Donation record via the Replace Payment Source page,

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is NOT a required field

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is a required field

    • When replacing the Payment Source of the records related to the Payment Source via the Replace Payment Source page,

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is NOT a required field

      • If the selected Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • If the selected Payment Method = Credit Card,

          • The Card CVV field is a required field

Bug Fixes

  • The Payment Source Retains after Changing an Existing Contact in Quick Donate 

    • When donating via the Quick Donate (Standard) page → Enhanced RD is disabled,

      • If an existing Contact record is selected AND an existing Payment Source record related to the Contact record is also selected,

        • When ANOTHER existing Contact record will be selected, the Payment Source field will be EMPTY so that the user can select a NEW Payment Source record that is related to the newly selected Contact record

    • When donating via the Quick Donate page → Enhanced RD is enabled,

      • If an existing Contact record is selected AND an existing Payment Source record related to the Contact record is also selected,

        • When ANOTHER existing Contact record will be selected, the Payment Source field will be EMPTY so that the user can select a NEW Payment Source record that is related to the newly selected Contact record

  • Card CVV is not required in Quick Donate

    • When donating via the Quick Donate (Standard) page → Enhanced RD is disabled,

      • If an existing Contact record is selected AND an existing Payment Source record related to the Contact record is also selected,

        • When the user deletes the selected payment source, the Card CVV is required based on the selected Gateway (PayDock, SecurePay, BPoint & eWay Purchase Type).

      • When donating via the Quick Donate page → Enhanced RD is enabled,

        • If an existing Contact record is selected AND an existing Payment Source record related to the Contact record is also selected,

          • When the user deletes the selected payment source, the Card CVV is required based on the selected Gateway (PayDock, SecurePay, BPoint & eWay Purchase Type)

2.208 - 2.210 (05/06/2024)

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

Required packages

ProntoPayments 2.85.119 or higher

Enhancements

  • Insufficient Guest User Permission when using CheckOut Page in WIT

    • Guest users have the same behavior as the admin user as the rest of the jobs are responsible for the payment processing in WIT when Process Immediately is ticked in ProntoGiving Settings

  • Added Mobile field as Available to use in BDE Contact Details Field Sets in the Contact Object

2.211 (28/06/2024)

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

Required packages

ProntoPayments 2.85.119 or higher

Enhancements

  • Unrequire CVV in Quick Donate for SecurePay Gateway

    • When donating via the Quick Donate page → Enhanced Recurring Donation is enabled,

      • If the selected Gateway record has a Record Type = SecurePay

        • The Card CVV field is NOT a required field

      • If the selected Gateway record has a Record Type != SecurePay,

        • The existing behaviour of the Card CVV field will be followed depending on the selected Gateway record

    • When donating via the Quick Donate (Standard) page → Enhanced Recurring Donation is disabled,

      • If the selected Gateway record has a Record Type = SecurePay,

        • The Card CVV field is NOT a required field

      • If the selected Gateway record has a Record Type != SecurePay,

        • The existing behaviour of the Card CVV field will be followed depending on the selected Gateway record

Web Integration Toolkit (WIT)

1.91 - 1.92 (31/05/2024)

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

Required packages

  • ProntoPayments 2.85.119 or higher 

  • ProntoGiving 2.207 or higher 

  • ProntoPlus 2.88 or higher  

Enhancements

  • eWay Transaction Type - Require CVV Validation (WIT)

    • When creating/updating a Campaign record,

      • If the Campaign’s Credit Card Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • When saving,

          • Regardless of whether the Campaign’s Require CVV is TRUE or FALSE, the Campaign record is saved successfully

      • If the Campaign’s Credit Card Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • When saving,

          • If the Campaign’s Require CVV is TRUE, the Campaign record is saved successfully

          • If the Campaign’s Require CVV is FALSE, an error message will display: Require CVC should be enabled as the selected Gateway requires a CCV.

Bug Fixes

  • Credit Card Auto Fill Validation in ASPaymentMethod

    • If the user auto-fills the credit card details with an incorrect expiry date,

      • The screen proceeds to the next error screen

    • If the user auto-fills the credit card details with the correct expiry date,

      • The existing functionality occurs

  • Invalid Card Expiry year but still payment goes through

    • If the user enters an incorrect expiry date, the payment will not proceed

1.93 (14/06/2024)

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

Required packages

  • ProntoPayments 2.85.119 or higher 

  • ProntoGiving 2.207 or higher 

  • ProntoPlus 2.88 or higher  

Bug Fixes

  • Google Pay in Production pointing to Test Environment

    • If Google Sandbox is enabled,

      • If the user clicks Donate with GPay button, Google Pay points to the Test Environment.

    • If Google Sandbox is disabled,

      • If the user clicks Donate with GPay button, Google Pay points to the Production/Live Environment.