This release is currently in testing and some of the items might not make to the final release.
Stripe Specific
- For the Stripe external webhook, merchant fees were not populating when a new payment transaction was created. This item is addressed as part of this release.
- For the Stripe external webhook, the country code was getting stored instead of the country in the payment txn. This item is addressed as part of this release.
- If the Stripe merchant facility doesn't have any payment gateway option, then the import file did not create line items. This item is addressed as part of this release.
- No error was getting logged when the payment complete webhook faced an issue while creating/updating the payment txn. This item is addressed as part of this release.
- The direct debit checkout form was not working when hideContactDetails is passed as a URL parameter. This item is addressed as part of this release.
- For direct debit. In some cases generic response code/description was being stored in the payment txn field. Now, we are extracting the response code, description from the gateway response and storing it.
- Account Update button was not showing the proper error in case of a missing email. This item is addressed as part of this release.
- Introducing PAD (Pre-authorized debit payment) payment ability for Stripe SCA
Blackbaud Specific
- Recurring Payment Processor, due to a token storage internal error, transactions are being marked as errors, but in fact are banked. This item is addressed as part of this release.
- The checkout form was not working when hideContactDetails was passed as a URL parameter. This item is addressed as part of this release.
- Previously, in some cases generic response code/description was being stored in the payment txn field. Now, we are extracting the response code, description from the gateway response and storing it.
- Previously, a temporary token was used and then updated to a permanent token for the checkout transaction. Now, we are not using any temporary token.
- A new payment gateway option, “Recurring Back Office,” is introduced. This enhances the recurring payment processor, especially the processing of expired cards.
- Custom metadata record stores Blackbaud token, updation of this metadata will only be done in the context authorised Payments2Us user. This significantly reduces the errors for standard/community users.
- Introduced new logging capability to store 500 error requests and the response body from the payment gateway.
- Additional error logging is done in order to capture any discrepancies.
General Updates
- Increase timeout for non-profit cloud business process API callouts.
- Handled scenarios based on the amount and donation so that gift transaction, gift commitment, and opportunity, opportunity line item records are created properly.
- Account Matching method was not getting set properly on the non-profit cloud org. This item is addressed as part of this release.
- Ezidebit card update was not working properly, especially if the billing token is missing. This item is addressed as part of this release.
- Payment day was sometimes getting set to today's date in the import file. This item is addressed as part of this release.
- Updated the Ezidebit payments processor to cater to today's transactions as well. Previously, it was only working for transactions until the last day.
- Datatools' address population was not working properly for some countries in the checkout form. This item is addressed as part of this release.
- Added a check to not perform address validation updates if the user doesn't have access to the merchant facility. This is done in order to avoid Payments2Us related errors for non-Payments2Us users on account, contact & lead records update.
- Token Charge Invocable method now can receive amounts and donation amounts in decimals as well.
- Introducing Archive Payment Txns/Items Feature: Now you can archive historical Payment Txns and Payment Items. It improves performance, makes day-to-day Payment Txns processing faster and reduces custom objects storage.
- Introducing CPI Price Increase feature for Recurring Payments: This feature enables you to set up annual CPI-based percentage increases to Recurring Payments, ensuring donor contributions stay in line with inflation or annual adjustments.
- Introducing Health Check for Payments2Us App: This feature is similar to Salesforce Health Check, but for Payments2Us. It helps you scan for common setup and configuration issues with the Payments2Us App in your org. The identified issues are logged with a brief description AND steps to resolve the problem.
- Introducing Automatic Membership Price Increase feature for Memberships/Subscriptions: This feature enables you to bulk apply change schedules to subscriptions/memberships against the membership types (payment options) automatically. It simplifies the process to update renewal pricing for multiple Subscriptions/Memberships.
- Introducing Subscriber Check-in System, it is a comprehensive solution designed for museums and similar institutions to manage member check-ins efficiently
Post Upgrade Steps
- For the membership check in to work properly with the site's guest user. Add 2 new values (AAkPay__Subscription__c, AAkPay__Account_Subscription__c) to Excluded from Sites Sharing Settings picklist field in Merchant Facility object.