Sorry, we didn't find any relevant articles for you.

Send us your queries using the form below and we will get back to you with a solution.

10.5 March 2025

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 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.

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.

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. 
    • A new custom metadata is introduced in order to store minimum amount for each currency with respect to the payment gateway.
    • For stripe, custom metadata records for some of the currencies are added as part of the package.
    • For any new such case, minimum amount, currency and payment gateway can be added as a custom metadata record in the org where package is installed. Example:
  • 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.
     

Updated at February 24th, 2025

Was this article helpful?