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
DataTools Kleber Address Validation now supports DPID (Delivery Point Identifier) validation when enabled on the Merchant Facility.
- A new option DPID has been added to the Validate picklist on the Merchant Facility.
- Checkout Forms now validates DPID when selected on the Merchant Facility.
- Account, Contact, and Lead Address Validation/Autocomplete can also validate DPID when enabled on the Merchant Facility.
- The Mass Address update & validate process can validate DPID information as part of address validation, when enabled on the Merchant Facility.
- The Data Validated field now correctly shows which fields have been validated (e.g. Phone, Mailing Address, Other Address, DPID, etc). This enhancement applies to Payment Txn, Contact, Account, and Lead object.
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.
Refunds LWC
The Refunds Lightning Web Component (LWC) provides an improved Lightning Experience interface for processing Payment Txn refunds.
- A quick action button Refunds have been added on the Payment Txn.
- It supports Credit Card Payment Txns refunds across the supported Payment Gateways.
- Refunds LWC calculations now correctly handles surcharge, service fee, and merchant fee.
- For more details, please review Refunds section.
Payment Txn Chargebacks
Payments2Us now supports Chargebacks (Disputes) for Stripe SCA and EziDebit Payment Gateway.
- A Chargeback Payment Txn is created when a dispute is lost, and the amount is refunded to the donor.
- The Chargeback Txn Amount includes the applicable chargeback penalty fees by the Payment Gateway.
- Chargeback Payment Txns are created with the Chargeback record type. The Transaction Source and Transaction Type are also set to Chargeback.
- Chargeback Txns can be found under the Refunds/Chargeback Txn's related list on Payment Txn.
- For more details, please review How does Payment Txn Chargebacks work.
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.
- Manual Payments now fully support Custom Lookup Fields. Review How to add or change fields on Manual Payments for more details.
- 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.
- Fixed an issue where users without the “View Setup and Configuration” permission received an "Attempt to dereference null" error when clicking the Annual Statement button on a Contact record. Refer to the help article for setup instructions.
- 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 (or activate) “DPID” and “Barcode” values to the Validate picklist field on the Merchant Facility object.
- Add “Chargeback” value to the Transaction Source and Transaction Type picklist fields on the Payment Txn Object. Please add picklist values to all record types.
- Add “Enable Chargebacks” option to the Payment Gateway Options picklist field on the Merchant Facility object.
- Update Field Dependency Payment Gateway → Payment Gateway Options. Add Enable Chargebacks for EziDebit Payment Gateway only.
- To enable Chargebacks for Stripe, add “charge.dispute.closed” event to the webhook. Please review Stripe Webhook Setup for more details.
- Add the WestPac Skip EntryMode value to the Payment Gateway Options picklist field on the Merchant Facility object.
- For customers using Xero with Payments2Us, all new and existing accounts/contacts marked for syncing to Xero should have “Xero Settings” lookup populated in order to avoid any validation errors.
- For Stripe users, please refer details in Stripe ACH eCheck API migration for steps you may need to follow to populate billing plan id on your current ACH eCheck recurring payments.
- Re-authorisation of Payments2us is recommended as enhancements in the authorisation process has been made as part of the release. Please refer to step 5.2 of following article for How to re-authorise Payments2us