Overview
Stripe has deprecated the Charges API for ACH payments. Payments2Us has updated the Stripe ACH eCheck integration to use Stripe’s Payment Intents API.
This article explains what has changed, which customers are affected, and what needs to be updated for existing ACH eCheck Recurring Payment records as part of post upgrade step of version 11.5.
This article applies only to customers using Stripe ACH eCheck payment functionality.
Use Case / Scenario
You may need this article if you are using Stripe as your payment gateway and process recurring ACH eCheck payments through Payments2Us.
After the migration to Stripe’s Payment Intents API, existing ACH eCheck Recurring Payments may need to be reviewed to confirm that the required Stripe values are stored correctly in Salesforce.
How this Works with Payments2Us
Payments2Us now supports the updated Stripe ACH eCheck integration using Stripe’s Payment Intents API.
The new ACH eCheck integration is only supported when Stripe SCA is selected as the Payment Gateway on the related Stripe Merchant Facility.
The updated integration also requires a Stripe Mandate ID. Stripe Mandate IDs usually start with: mandate_
For all new ACH eCheck Recurring Payments, Payments2Us will automatically store the Stripe Mandate ID in the following field on the related Recurring Payment record:
-
Billing Plan ID
(AAkPay__Billing_Plan_Id__c)
For existing integrations
For customers with an existing Stripe ACH eCheck integration, the recommended upgrade approach is to update the Gateway on the existing Merchant Facility from Stripe to Stripe SCA, rather than creating a new Merchant Facility with Stripe SCA.
Updating the existing Merchant Facility retains the existing relationships and configuration associated with that Merchant Facility and ensures that current Recurring Payments continue to use the correct gateway method.
Please note: This is a recommended approach based on a standard Payments2Us configuration. Each organisation may have its own business requirements, custom configuration, automation, recurring payment setup, and integrations. You should review your specific setup and business requirements before deciding on the appropriate migration approach. If you are unsure which approach is suitable for your organisation, please contact Payments2Us Support for assistance.
Steps
1. Confirm the Stripe Merchant Facility uses Stripe SCA
The updated Stripe ACH eCheck integration is only supported when the Payment Gateway on the Stripe Merchant Facility is set to Stripe SCA. If the Merchant Facility is not using Stripe SCA, ACH eCheck payments using the updated integration may not work as expected.
2. Confirm the Stripe Mandate ID is populated
For ACH eCheck recurring payments, the Stripe Mandate ID must be stored in the Billing Plan ID field on the related Recurring Payment record.
The value should start with:
mandate_
Field to update:
-
Recurring Payment > Billing Plan ID (
AAkPay__Billing_Plan_Id__c)
3. Review existing ACH eCheck Recurring Payments
The previous Stripe ACH eCheck implementation did not store the Stripe Mandate ID
These records need to be updated before they can use the new Stripe ACH eCheck integration correctly.
Existing ACH eCheck Recurring Payment records may have a blank Billing Plan ID field or may not contain the required mandate_ value.
4. Retrieve Mandate IDs from Stripe
Customers will likely need to work with Stripe to retrieve the correct Mandate ID values for their existing ACH eCheck recurring payments.
Once retrieved, populate the Mandate ID into the Billing Plan ID field on the related Recurring Payment records in Salesforce.
5. Confirm related Stripe values if needed
While discussing this with Stripe, it is also worth confirming whether any updates are required to the existing Stripe values stored in your Payments2Us records, including:
-
Customer ID values starting with
cus_ -
Payment Method ID values starting with
pm_
We do not anticipate changes being required for these values, but Stripe can confirm whether the existing values remain valid for your ACH eCheck payment setup.