#Kinno
1 messages ยท Page 1 of 1 (latest)
Hello ๐
I've not heard of any plans to deprecate Sources API anytime soon. However, if you're building a new integration then you should be using the PaymentMethods API instead.
do bacs_debit payments only work with Sources on connected accounts?
It seems to work for them but then fails when we tried to adjust our code to also work for internal payments :/
Not sure I completely follow the flow here, can you elaborate?
Aren't a lot of the Source APIs already considered deprecated? <.<
To elaborate on the main point:
We are using stripe connect and use the Source API for direct bacs payments,
when our connected accounts accept these payments there is no issue,
but when we try this with our platform account accepting payments from our connected accounts, it fails (IIRC with an invalid payment type error)
I was searching through the documentation a bit and going off comments in our code, it feels like the Source API doesn't actually support direct_bacs openly?
Aren't a lot of the Source APIs already considered deprecated? <.<
They are but it shouldn't be breaking existing integrations.
My confusion is partially found here https://stripe.com/docs/api/sources/object#source_object-type, since there is no bacs_debit payment type on the spec but it seems to work for our connected accounts in some "hacky" manner?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Are we perhaps using an option that's not available by default? If so is there a reason it's also not available for accepting payments on the platform account? ๐
Can you share a request ID where you're seeing an error?
I need to make sure I understand the usecase here before we dive deeper