# I received an email about migrating SuiteSync as part of my ACH Direct Debit migration. How is SuiteSync affected by the Charges API deprecation?

SuiteSync is one piece in your overall Stripe and NetSuite integration environment. Your unique integration may be utilising legacy ACH components including the Charges API in conjunction with SuiteSync. Use this guide to identify which of the following changes you need to make.
### Update SuiteSync payment surfaces
SuiteSync has several prebuilt payment surfaces that support legacy ACH. These include NetSuite payment links for invoices, sales orders and customer balance. These surfaces also have the ability to save payment methods for future auto charging.
Stripe Connector for NetSuite solves this issue by using new Payment Pages that utilise Stripe Checkout. All surfaces are updated and support ACH and Financial Connections. All payment methods saved for future auto charging include a fully compliant mandate. Other global payment methods are also now supported.
[Reach out to the Stripe Connector for NetSuite team](https://support.stripe.com/contact/login?redirected=true&topic=stripe_apps&app=netsuite&subject=%5BStripe+Connector+for+NetSuite+\(SCN\)%5D) to start your SuiteSync migration.
### Update previously saved legacy ACH payment methods for existing customers
SuiteSync has prebuilt workflows that automatically charge previously saved payment methods, including NetSuite Auto Pay and Triggered Payments. You may also have a custom workflow that auto charges payment methods previously saved to a Stripe customer. These workflows enable NetSuite subscription billing and other use cases.
If your integration previously saved legacy ACH payment methods for any of your customers, you'll need to update these payment methods to include a mandate before continuing to auto charge them. You don't need to reach back out to your existing customers to save their bank account information again. You can backfill mandates and migrate previously collected bank account details using the [Tokens API](https://docs.stripe.com/api/tokens). Learn more about the [process and options](https://docs.stripe.com/payments/ach-direct-debit/migrating-from-charges?integration-path=payment-intent).
Migrating from SuiteSync to Stripe Connector for NetSuite will also give you more control over your NetSuite Auto Pay and Triggered Payments workflows.
### Update custom-developed Stripe surfaces within your integration environment
SuiteSync recognises all payments and other object types created in your Stripe account by any surface, creating NetSuite record copies and triggering deeper automations for bank reconciliation and more. If your environment utilises any type of Stripe surface that still supports the Charges API, complete the steps in the [ACH Migration documentation](https://docs.stripe.com/payments/ach-direct-debit/migrating-to-new-apis):
1. Turn on **ACH Direct Debits** in the Stripe Dashboard.
1. Build your new integration with the [Payment Intents API / Checkout Sessions API](https://docs.stripe.com/payments/ach-direct-debit/migrating-to-new-apis).
1. Begin verifying new bank accounts and collecting ACH mandates with [Financial Connections](https://docs.stripe.com/financial-connections/ach-direct-debit-payments) or an alternative verification option.
1. Test the new integration.
Many custom-developed surfaces used in the same environment as SuiteSync utilise the addition of metadata. SuiteSync uses these [specific metadata keys](https://docs.stripe.com/use-stripe-apps/netsuite/custom-payment-application) and values to identify what type of NetSuite record to create, and if it should be applied to another transaction. Stripe Connector for NetSuite supports all of these metadata triggers and provides improved processing power for NetSuite record creation and automations.
### Update to the latest version of third-party surfaces that may be using the Charges API
Contact the developer to download their latest version. For more information, refer to the support article about third-party integrations and the ACH Direct Debits on Charges API shut down.