#ayesha-shaikh_api

1 messages ¡ Page 1 of 1 (latest)

river pilotBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1491813812431749301

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

keen silo
#

Hello
If you're just reteriving charges then it won't really impact you.
This change impacts folks who are still using the older Sources/Tokens API endpoints to tokenize the payment method

vestal cradle
#

my concern is that the email explicitly says

CDK Global is currently accepting ACH Direct Debits using the Charges API, a legacy integration that will no longer be supported on May 15, 2026. After this date, if you do not upgrade your integration, any Charges API calls for ACH Direct Debits will fail.

#

this is the email we got

keen silo
#

Can you share your account ID?

vestal cradle
#

okay

keen silo
#

If you don't use the Charges API to charge users really then you can ignore the email

vestal cradle
#

acct_1InFxgGXlQ7PG1un

keen silo
#

ah. I think you got the email because this charge was paid through a BankAccount object - py_3THn4nGXlQ7PG1un2V6iVNqR