This release is currently under development and some of the features might not make it to the final release.
Wesptac Quickstream Automated Direct Debit
- Payments2Us now supports automated direct debit for the westpac quickstream payment gateway. For details review the Direct Debit help articles.
- Enable "BECS" in the field "Payment Gateway Options" field of your westpac merchant facility record in order for the automated direct debits to work.
Stripe ACH eCheck API migration
Stripe has deprecated the Charges API for ACH payments. Payments2Us has updated the Stripe ACH eCheck integration to use the Payment Intents API.
- The new integration is only supported when Stripe SCA is selected as the Payment Gateway on the Stripe Merchant Facility.
- The new integration requires a Stripe Mandate ID (starting with mandate_).
- For all new ACH eCheck recurring payments, the Mandate ID will be automatically stored in the Billing Plan ID (AAkPay__Billing_Plan_Id__c) field of the related Recurring Payment record.
Existing Recurring Payments
For recurring payments created prior to this upgrade, the Mandate ID is not stored by the previous implementation. You will need to contact Stripe to obtain the corresponding Mandate IDs and populate them in the Billing Plan ID (AAkPay__Billing_Plan_Id__c) field of the related Recurring Payment records. The following recurring payment fields should contain the Stripe identifiers:
- Payment Gateway Customer Profile ID (AAkPay__Payment_Gateway_Customer_ProfileId__c) → Stripe Customer ID (cus_)
- Billing Token (AAkPay__DpsBillingId__c) → Stripe Payment Method ID (pm_)
- Billing Plan ID (AAkPay__Billing_Plan_Id__c) → Stripe Mandate ID (mandate_)
Address Finder DataTools Kleber Validation
- Added “DPID” picklist option to the Validate field on the Merchant Facility Object.
- Checkout Form now allows for DPID to be validated by dataTools, when selected under “Validate” field on the Merchant Facility.
- Account, Contact and Lead Address Validation also allows for DPID validation, when selected under “Validate” field on the Merchant Facility.
- Mass Address update & validate now validates DPID as part of “Mass Update Address”, when selected under “Validate” field on the Merchant Facility.
- Data Validated field on Payment Txn, Contacts, Accounts and Leads now correctly shows which fields have been validated (e.g. Phone, Mailing Address, Other Address, DPID, etc).
Westpac Entry Mode Parameter
As per the latest Westpac API changes, the entryMode parameter is now required for Backend Transactions API requests. Payments2Us has been updated to automatically include this parameter in applicable backend transaction requests.
If you experience any issues after this change select the WestPac Skip EntryMode option on your Westpac Merchant Facility record. When this option is enabled, Payments2Us will not send the entryMode parameter in backend transaction requests.
Xero Updates:
- New record type is introduced in Xero Invoice/Credit Note object. Record type name is “Xero Bill”.
- If record type is Xero Invoice, then an invoice will be created in Xero during syncing, otherwise if record type is “Xero Bill” then a Bill will be created/synced to Xero.
- Moreover, new lookup field “Xero Settings” is introduced on the account object, in order to sync any account or contact with Xero, this lookup need to be populated as well. Otherwise a validation error will be thrown when you try to Mark account/contact for Xero Sync.
Transact Payment
- Payment method-specific fields are now automatically cleared when the user changes the payment method.
- Cheque details are removed when switching to Cash or Credit Card payments.
- Cash-specific values are cleared when changing to another payment method.
- The Transact Payment component has been updated to prevent data from a previous payment method from being carried over into a new transaction.
- Payment record values are also reset during reinitialization after a transaction is successfully saved, ensuring stale data is not retained for subsequent transactions.
General Updates
- Resolved the domain mismatch error that occurred on the internal payment forms using the Windcave payment gateway with Google/Apple Pay payment options enabled.
- The manual Contact Reconciliation process was not displaying the success page upon completion. This issue has been resolved.
- The TxnRef field on the Payment txn record was being cleared when Stripe returned a failed or error response. The field will now remain populated regardless of the transaction outcome.
- For Stripe Direct Debit payments, the returned masked bank account details (Account Number and BSB Number) are now stored in the corresponding fields on the Payment txn/Recurring payment records.
- For Windcave PxPay, email address and/or phone number are mandatory fields for 3D Secure authentication. Payments2Us now sends this information as part of the Windcave PxPay request. Customers are strongly encouraged to make these fields mandatory on their checkout forms as well.
- When cloning a Payment Form, encrypted fields such as the Webhook Secret Key and URL Parameter Encryption Keys were not being copied correctly. This issue has been fixed.
- Custom Lookup Fields were not returning search results on the Manual Payments. Now custom lookups are fully supported on manual payments component.
- Recurring eCheck payments generated duplicate Payment Txns while awaiting settlement.The Transaction Generated flag now persists for pending eCheck transactions.
- A new field, Amount Limit, has been added to the Surcharge object. If left blank, existing behaviour remains unchanged. When populated, the Surcharge or Cover Transaction Fee calculation will only be applied if the payment amount is less than the specified Amount Limit value.
- When values containing special characters such as apostrophes (') or ampersands (&) were passed via URL parameters (for example, FirstName, LastName, or CompanyName), the characters could be converted into URL-encoded values (for example, %27). This issue has been addressed.
- Batch processor was logging “Argument cannot be null” error and payment txns were getting stuck at Receipting Complete in a special case. This issue has been resolved now.
- An unclear error log could be generated when the Public Site Guest User did not have access to a Campaign record. To improve troubleshooting and visibility, Payments2Us now includes the related Campaign ID in the error log details.
- The Refresh Token Rotation implementation introduced in version 11.4 has been further enhanced to reduce the likelihood of reauthorisation being required due to token refresh conflicts or race conditions.
Post-Upgrade Steps:
- Add “Chargeback” picklist value to the
Transaction SourceandTransaction Typepicklist field on the Payment Txn Object. Please add picklist value to all record types. - Add (or activate) “DPID” and “Barcode” picklist values to the
Validatefield on the Merchant Facility Object. - Add the WestPac Skip EntryMode value to the Payment Gateway Options picklist field on the Merchant Facility object.