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 9 Next »

Product releases in this quarter

ProntoPayments 2023 Q4 release notes are located in the ProntoPayments v2 section

ProntoGiving

2.203 (13/12/2023)

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

Required packages

ProntoPayments 2.85.108 or higher

Bug Fixes

  • Payment Source Response is Successful but Processing Status is failed in BDE Item

    • When processing a BDE Item record where Gateway is SecurePay and Tokenization Payment is TRUE,

      • If Frequency is Monthly, Processing Status in BDE Item should be Processed

Enhancement

  •  Enhance Card CCV Field in Replace Payment Source

    • When replacing a new Payment Source record via Replace Payment Source in a Recurring Donation record,

      • If the selected payment method option is a Credit Card,

        • If the selected Gateway record is EziDebit,

          • The Card CCV field will display as a required field

        • Otherwise,

          • The Card CCV field will display but NOT a required field

Web Integration Toolkit (WIT)

1.75 (5/10/2023)

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

Required packages

  • ProntoPayments 2.85.93 or higher  

  • ProntoGiving 2.186 or higher 

  • ProntoPlus 2.85 or higher  

Bug Fixes

  • CheckOut Page ASPaymentMethod Error 

    • If a user enters the credit card details inside a record, 

      • No Script error message was shown  

      • Successfully process the payment 

1.76 (1/11/2023)

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

Required packages

  • ProntoPayments 2.85.103 or higher 

  • ProntoGiving 2.202 or higher 

  • ProntoPlus 2.88 or higher 

Bug Fixes

  • Direct Debit Fields Validation Not Showing 

    • When a user inputs an invalid direct debit validation, 

      • An error message was shown 

      • Give now button was disabled 

Enhancement: 

  • ASPaymentMethod CSS Styling Enhancement 

    • If the Payment Method in the campaign is set to only one option (ie. Credit Card) for both recurring and once-off donations

      • The payment option buttons will disappear 

      • The spacing will be changed or have a normal space gap 

  • Additional Aura Component Design Attributes For PaymentDetails 

    • The AsFlowFooterButton component is updated where: 

      • If the user hits a validation, the PaymentDetailsValidation will be set to TRUE 

      • If the component disabled the button (Give Now) as the user hits a validation, the HasValidation will be set to TRUE

      • Configuration 

  • Give Now Button Visibility on Screen Flow 

    • The AsFlowFooterButton component is updated where: 

      • If isHideGiveNowButton is TRUE, 

        • Give Now button will be hidden 

      • If isHideGiveNowButton is FALSE, 

        • Give Now button will be display 

1.77 (18/12/2023)

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

Required packages

  • ProntoPayments 2.85.108 or higher 

  • ProntoGiving 2.203 or higher 

  • ProntoPlus 2.88 or higher

Enhancement: 

  • Display Comments Field Regardless of the Frequency

    •  If the Campaign’s Display Comments Field is TRUE,

      • Regardless of the value of the Multiply my gift by making it a monthly donation checkbox, the Comments field will display

    • If the Campaign’s Display Comments Field is FALSE,

      • Regardless of the value of the Multiply my gift by making it a monthly donation checkbox, the Comments field will be hidden

  • Choosing Receipt Action on CheckOut Page

    • When the Checkout Page loads (without the Receipt Action URL parameter),

      • After providing the necessary details for a donation, a BDE Item record will be created where the Receipt Action = Email

    • When the Checkout Page loads (with the Receipt Action URL parameter where the value is VALID),

      • After providing the necessary details for a donation, a BDE Item record will be created where the Receipt Action = based on the Receipt Action URL parameter

    • When the Checkout Page loads (with the Receipt Action URL parameter where the value is INVALID),

      • After providing the necessary details for a donation, a BDE Item record will be created where the Receipt Action = Email

    • Configuration

  • Apply Australian Bank Account Validation to WIT Donation Pages

    • If the selected payment method option is Direct Debit,

      • If Australian Bank Account Validation is ENABLED in the ProntoPayments Settings

        • If Account Number is less than 6 digits OR exceeds 9 digits, an error message will display

        • If Account BSB is less than OR exceeds 6 digits, an error message will display

      • If Australian Bank Account Validation is DISABLED in the ProntoPayments Settings,

        • If Account Number is less than 6 digits, an error message will display

        • If Account BSB is less than 6 digits, an error message will display

Configuration Notes

Additional Aura Component Design Attributes For PaymentDetails

The goal of this documentation is to guide the client in customizing the WIT CheckOut Page. This involves configuring it to employ the standard Salesforce button instead of the Give Now button within the screen flow.

To enable the use of the standard Salesforce button, we have introduced specific attributes to the AsFlowFooterButton component:

  • PaymentDetailsValidation: This attribute is used for payment validation

  • HasValidation: It's employed for comprehensive validation

  • Hide Give Now Button: This attribute allows you to conceal the Give Now button.

To make the Give Now button disappear and utilize the standard Salesforce button, simply set the Hide Give Now Button attribute to "True."

To display the Give Now button, set the Hide Give Now Button attribute to "False."

To execute a payment using the standard Salesforce button while retaining the validation, the client has the option to select from these two alternatives:

Utilise HasValidation attribute to apply validation to the entire CheckOut Page.

Enable Manually assign variables in AsFlowFooterButton component

Create a new Boolean variable to pass the HasValidation value in AsFlowFooterButton component

Get Decision element to check if the validation occurs during filling up the donor or payment details before clicking the button

If the validation is True, it would go back to the form and the error message displayed

Using Set Component Visibility for displaying error message

Before:

After:

If the validation is False, the payment has successfully processed

Before:

After:

Use PaymentDetailsValidation only when ASPaymentMethod is being used entirely as the Payment Details validation.

When configuring PaymentDetailsValidation attribute, follow the same procedures as before:

Before:

After:

Invalid Donor Details were already included in the WIT CheckOut Page. Its purpose was to validate the Donor Details only.

Like PaymentDetailsValidation, when configuring Invalid Donor Details attribute, follow the same procedures as before.

Choosing Receipt Action on CheckOut Page

Here are some configurations to choose which Receipt Action to use:

  • Input Receipt_Action variable in the URL Filter Parameters of the CheckOut Page in Experience Builder

  •  If the user inputs the Default Value of the Receipt_Action variable to Do Not Receipt

    •  After processing the payment on the CheckOut Page

  • The user can add the Receipt Action in the CheckOut Page URL

    • Copy the Campaign URL or click the Campaign URL

    • Paste the URL and add the Receipt_Action variable

    • After processing the payment on the CheckOut Page,

  • No labels