| Info |
|---|
ProntoPayments 2024 Q3 release notes are not available yet. For the latest version, see ProntoPayments v2 section |
| Info |
|---|
Importance Notice
|
ProntoGiving
2.212 - 2.213 (02/08/2024)
URL: /packaging/installPackage.apexp?p0=04tIT000001ZeL3
...
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
...
Opportunity Receipt Number Auto-Number
NOTE: After installing this version, do this 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
...
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
...
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
...