• ProntoGiving

  • 2.212 - 2.213 (02/08/2024)

• ProntoPlus

  • 2.94 (26/7/2024)

• Web Integration Toolkit (WIT)

  • 1.94 (19/07/2024)

  • 1.95 (08/08/2024)

  • 1.96 (26/09/2024)

ProntoGiving

2.212 - 2.213 (02/08/2024)

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

Required packages

ProntoPayments 2.85.119 or higher

Enhancements

• Batch Payment Processing - Open Opportunity Stage for Direct Debit Payments Using SecurePay

  • When processing Direct Debit payments via the Batch Payment Processing in the ProntoPayments Settings → Scheduler,

    • The payment will be processed (internal)

    • If the Payment Transaction’s Payment Status = Success,

      • If the Gateway = SecurePay,

        • The Payment Transaction’s Opportunity → Stage is NOT be updated (stays to open)

      • If the Gateway != SecurePay,

        • The existing functionality will be followed where the Payment Transaction’s Opportunity → Stage is updated:

          • Based on the ProntoGiving Settings custom setting’s Opportunity Won

          • Based on the Payment Transaction’s Gateway → Default Stage for Successfully Processed

          • To Closed Won (default)

    • If the Payment Transaction’s Payment Status = Failed,

      • Regardless of the Gateway,

        • The existing functionality will be followed where the Payment Transaction’s Opportunity → Stage is updated:

          • Based on the Payment Transaction’s Gateway → Default Stage for Failed Processed

          • Based on the ProntoGiving Settings custom setting’s Opportunity Lost

          • To Closed Lost (default)

Bug Fixes

• Batch Payment Processing - Opportunity not updated to Closed Lost

  • When processing Direct Debit payments via the Batch Payment Processing in the ProntoPayments Settings → Scheduler,

    • The payment will be processed (internal)

    • If the Payment Transaction’s Payment Status = Failed,

      • Regardless of the Gateway,

        • The existing functionality will be followed where the Payment Transaction’s Opportunity → Stage is updated:

          • Based on the Payment Transaction’s Gateway → Default Stage for Failed Processed

          • Based on the ProntoGiving Settings custom setting’s Opportunity Lost

          • To Closed Lost (default)

ProntoPlus

2.94 (26/7/2024)

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

Upgrade Risk For installation or upgrade to version 2.57 or higher, please make sure to reschedule the receipting batches  

• Send Receipts  

• Generate Receipts 

Enhancements

• Opportunity Receipt Number Auto-Number

  • NOTE: After installing this version, do this configuration

    • Opportunity Receipt Number Configuration

  • When installing the new ProntoPlus version to a clean org,

    • On the Opportunity object, a NEW Receipt Number (auto-number) field is created where the starting number is 1

    • Whenever an Opportunity record is created, the value of the Receipt Number (auto-number) field will be incremented by 1 automatically

    • When generating and sending a receipt,

      • The receipt number of the receipt will be based on the Opportunity’s Receipt Number (auto-number) field

  • When installing the new ProntoPlus version to upgrade the current version to an org,

    • On the Opportunity object, a NEW Receipt Number (auto-number) field is created where the starting number is based on the ProntoPlus Settings custom setting’s Next Receipt Number field

    • Whenever an Opportunity record is created, the value of the Receipt Number (auto-number) field will be based on the ProntoPlus Settings custom setting’s Next Receipt Number field

    • When generating and sending a receipt,

      • The receipt number of the receipt will be based on the Opportunity’s Receipt Number (auto-number) field

Web Integration Toolkit (WIT)

1.94 (19/07/2024)

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

Required packages

• ProntoPayments 2.85.119 or higher 

• ProntoGiving 2.207 or higher 

• ProntoPlus 2.88 or higher  

Bug Fixes

• Auto-filled Credit Card Validation is not working

  • If the user auto-fills the credit card details

    • If the mouse hovers over the Expiry Date (MM/YY) and changes the value with an incorrect Expiry Date (MM/YY)

      • When the Screen Flow Standard Button is clicked,

        • The screen proceeds to the next error screen “Invalid payment. Please try again”.

  • If the user manually inputs the credit card details;

    • If after the Cardholder Name is inputted, using the Tab key inputs the Card Number, the Expiry Date (MM/YY) value with an incorrect Expiry Date (MM/YY), and the CVV number

      • When the Screen Flow Standard Button is clicked using the Tab key,

        • The screen proceeds to the next error screen “Invalid payment. Please try again”.

  • If the user auto-fills the credit card details with the correct Expiry Date (MM/YY),

    • When the Screen Flow Standard Button is clicked;

      • The existing functionality occurs

  • If the user manually inputs the credit card details with the correct Expiry Date (MM/YY),

    • When the Screen Flow Standard Button is clicked;

      • The existing functionality occurs

  • If the user manually or auto-fills the credit card details with incorrect Expiry Date (MM/YY),

    • When the Give Now Button is clicked,

      • The existing functionality occurs

1.95 (08/08/2024)

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

Required packages

• ProntoPayments 2.85.119 or higher 

• ProntoGiving 2.207 or higher 

• ProntoPlus 2.88 or higher  

Bug Fixes

• Incorrect Google Pay Merchant Credentials used in Production Environment

  • If Google Sandbox is enabled,

    • The existing functionality occurs in which the environment is a test environment and using test Google Pay merchant credentials

  • If Google Sandbox is disabled,

    • It will switch to the Production Environment and get the Google Pay Merchant Name and Google Pay Merchant ID in Web Toolkit Settings

1.96 (26/09/2024)

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

Required packages

• ProntoPayments 2.85.119 or higher 

• ProntoGiving 2.207 or higher 

• ProntoPlus 2.88 or higher  

Bug Fixes

• Google Pay Transaction not charging the correct amount including cents

  • If a user transacts an amount with cents using Google Pay,

    • The amount being charged to Stripe is the amount not including the cents

    • This issue is now fixed

Opportunity Receipt Number Configuration

In this functionality, we decided to Deprecated Receipt Number (PPlus) in Opportunity and instead, we used the Custom Auto Number Field as a Receipt Number.

After installing ProntoPlus 2.94, these are the steps you need to do to use the Receipt Number Auto Number Field:

• Click the Setup Gear > Developer Console > Debug > Open Execute Anonymous Window

  • Paste this code: ProntoPlus.GlobalFunctions.createReceiptNumberField();

• It will create the Receipt Number located in the Opportunity Object

  

• Make sure to give access to the new Receipt Number (auto-number) field

  • Setup > Users > Profile > System Administrator > Object Settings > Opportunity
    

• Add Receipt Number (auto-number) field in the Opportunity Page Layout

  

• When installing the new ProntoPlus version to a clean org,

  • When creating a new Opportunity record, a new Receipt Number (auto-number) field is created where the starting number is 1

    

• When installing the new ProntoPlus version to upgrade the current version to an org, a new Receipt Number (auto-number) field is created where the starting number is based on the ProntoPlus Settings custom setting’s Next Receipt Number field