This release is currently under testing. Some of the list features might not make it to the final release.
Salesforce Security Review Changes
- Many backend enhancements have been implemented to further strengthen the app’s security and improve overall performance.
Stripe SCA Direct Debit Import
- Direct debit import was not working properly for Stripe SCA Direct Debit. Tokens were not getting set properly in payment txn and recurring payments
- Now, import file feature can be used for Stripe SCA Direct debit.
- Review Payments2Us help article listing Stripe Compliance's before using Direct Debit Import File feature for Stripe SCA.
Shopify Custom Fields
- As part of this release we have integrated the ability of storing custom metadata/fields/properties from shopify to payment item record in salesforce.
- Review Payments2Us help article for required configurations.
General Updates
- For Xero connection, now only selected organisation/tenant is shown on the success page and also only the selected tenant/organisation is synced against the Xero settings as well.
- For Xero connection, refresh token is now stored more securely inside protected custom metadata record.
- A new license “Production Allowed” was introduced in version 10.2, this license is needed to connect to a production payment gateway environment on a sandbox or DE org.
- Some fixes and enhancements are done for the advance styling in the payment forms.
- Amount can be displayed in decimal format as well in the button.
- Expiry date alignment issue is resolved now.
- Resolved issue of payment frequency picklist values getting double if labels are changed (i.e. “05” to "5th of Month")
- Amount tokenisation was not working for Stripe if the currency is JPY. Issue is resolved and new configurations are introduced for storing minimum charge amounts.
- Stripe FPOS integration, now sets more fields like Production Id and SKU on the payment item record.
- Previously, Stripe FPOS integration only used to work if the Stripe's merchant facility is set to Primary. Now it will work correctly even if the merchant facility not a primary one.
- Ezidebit payment gateway processor in now correctly setting the Payment Status to “0” or “1” as well along with the other payment related fields.