#john-payments-ach
1 messages ยท Page 1 of 1 (latest)
Hey there
Hello!
Does that Customer have a default_source set?
hmm, this is what the customer has for details
where would I see that default_source?
Ah okay
So that ACH bank account is a PaymentMethod (see pm_xxx)
This is our newer API/integration
It isn't compatible with our legacy integration, which uses the Charges API
If you want to charge that PaymentMethod then you need to use the PaymentIntents API
Is there a way to import and/or add ACH details manually with the charges API?
we're using the Stripe for NetSuite integration and they use the charge API. So want to make sure everything is aligned using the same thing
You would create a bank account object in that case: https://stripe.com/docs/api/customer_bank_accounts/create
That bank account object is our legacy ACH object and compatible with the Charges API
That is assuming you have the account and routing numbers of your customer's accounts already?
correct
You also are going to need to handle verifying the account.
Which is done via microdeposits with this legacy integration
got it. Is there a way to manually add an account this way?
or just via integration?
By "manually" I assume you mean via the Dashboard?
correct
Gotcha then no. You have to use the API here as the Dashboard uses our newer PaymentMethods API
got it. Sounds like we might want to use the PaymenthMethods API for the call. Do you have documentation on that?
Does that require us to send the card/ach we want or can it take the default on file?
Hmm I'm a bit confused now.
You want to be compatible with the Charges API? Or is that not a concern?
If we switch our API to use PaymentMethods instead of Charges with our customer I sent earlier would it work?
Hopefully that makes sense ๐
john-payments-ach
@analog kite yes you need to follow the docs for this really https://stripe.com/docs/payments/ach-debit
Thanks. We may just use our Charges API. Going back to the bank account object. If we import our ACH details, we can import those as this object, right?
what does that mean "If we import our ACH details"? Import from where?
We are importing account number, routing number over to Stripe from our old provider. I'm assuming as part of this process we just need to ensure this gets created in Stripe as a Bank Account object?
Who is importing though? You? With real code? Or Stripe's migrations team?
stripes migration team. We are just providing them the data
and it sounds like when they import we need those to be created as Bank Accounts so we can use the old Charges API
Gotcha so then yes that's what you want. Or really fix your integration to not use the legacy Charges API that was deprecated multiple years ago
LOL blame the Stripe for NetSuite connector! they are the ones using the old API ๐ฆ
I'm glad they told us about this Discord though. You have been greatly helpful! You wouldn't know what metadata we need to add to paymenth methods if a card fails so when we call with the charges API it uses the next (valid) ACH/CC?
or if there's a way to use the charges API and pick up the default card/ACH on file?
I'm fairly certain with have a Netsuite app that uses PaymentIntents and PaymentMEthods properly. I'd recommend talking to our support team. We don't know much about this here as we focus on helping developers with their own code
You wouldn't know what metadata we need to add to paymenth methods if a card fails so when we call with the charges API it uses the next (valid) ACH/CC?
there's no such thing at all in our products so you'd need to build this retry/fallback logic yourself from scratch
Sounds good. That should do it. I appreciate the assistance!
Sure thing!
have a nice day
you too ๐
One last question, if Stripe is handling our data migration and we use bank accounts we still have to verify the account? (aka get he microdeposits and validate) There's no way around this?
Depends where the data comes from but in theory if Stripe imports the data they skip micro-deposits since you would have proof you collected and verified those before. But it's really something to discuss directly with the migrations team