#CodyL - payment intent migration
upbeat minnow
prisma river
With sources we could query the customer and expand the sources which would give us all the sources attached to the customer.
upbeat minnow
No, that's not yet supported on Payment Intents/Payment Methods
prisma river
@upbeat minnow ok yeah it wasn't clear on https://stripe.com/docs/payments/sources/credit-transfers if there was a beta based on the last section
What about quering the Payment Methods on a customer?
upbeat minnow
Bank transfers refers to this: https://stripe.com/docs/payments/bank-transfers/accept-a-payment
For listing payment methods, yes you must specify a type to list
If you want to preverse a unified list, you could cache the necessary details in your own system to return directly when needed
prisma river
OK. Not ideal but I guess we will just have to make quite a few request when presenting the payment methods to a customer
It would appear that the bank transfers is only for one time payments and not recurring
where the current ach credit transfer sources works for ongoing payments
upbeat minnow
Recurring subscription payment should be supported: https://stripe.com/docs/payments/bank-transfers#subscriptions
What leads you to believe that is not the case?
prisma river
because they way to set it up is a payment internet and not a setup intent
When setting up for a customer we would not know what the amount would be.
With sources we are bascially just creating a virtual bank account that the customer pushes money into (based on our invoices, not using stripe invoices)
we are then notified that money has been deposited and then we make a charged based on that source.
Often the customers accounting deparement will want to load us as a vendor in their accounting system before we have even sent them their first invoice and to do that they will want the routing and account numbers for where to transfer the money
The overap between Credit Transfers and Bank Transfers is confusing to say the least.
upbeat minnow
It's a different integration, yes, but I'd recommend reviewing that guide to understand the expected flow
prisma river
yeah doesn't currently seem possible
or isn't documented well
guess we will leave it as sources for now for the ACH Credit Transfer
and I've submitted a feature request to return a unified list of payment methods attached to a customer
upbeat minnow
I expected this guide would cover what yopu're looking for: https://stripe.com/docs/billing/subscriptions/bank-transfer but if some piece of that is not doing what you expect while testing please let us know!
prisma river
Well we don't use Stripe billing/subscriptions
proven light
catching up here one sec
prisma river
ok
Just to set the background we are an established stripe customer which processes about 4600 payments per month. ~1000 card, ~3500 ACH Debit and ~100 ACH Credit
for about 1.2M USD
we sell phone services o our customers are with us month over month
and we charge them either auto pay or sending them to a payment page whcih shows all their attched sources so they can pick which source and what amount to charge
We handle our own invoicing outside of stripe and only use stripe for payments.
I'm in the process of converting our integration to use the new PaymentMethods/Intents API for compliance with the new ACH Debit rules
It would appear that we need to stay on Sources for ACH Credit at this point. Is that correct?
And the other feedback would be that for customers like myself not having a unified way to pull down payment methods from a customer like we currently do for sources is a real step back.
proven light
checking something
I believe there is a beta for ACH Credit on PaymentMethods API, not sure if they're taking new users or not but if you have a sales/account contact internally, recommend reaching out to them about access to the beta
or just reach out to Stripe Support letting them know you're looking for beta access and the Stripe developers here in Discord recommended you there
prisma river
OK, thanks