#deepstitch - Create Source Error
1 messages · Page 1 of 1 (latest)
HI 👋
Do you. have a request ID for the failed request?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Yes, thanks - it's req_Inraf2MgUdLrL2
Oddly enough it's the Customer parameter that is unknown, see the acceptable parameters here: https://stripe.com/docs/api/sources/create
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
the documentation states that the customer parameter should be set in the request
Can you share that doc?
scroll to the "Cloning Card Sources" section and choose the "Java" tab
actually, all tabs indicate that the customer id should be included in the request
Yep you are correct
And so when you used .setOriginalSource it passed in a token parameter?
Since we started this chat, I've tried several things because I'm up against the clock
Here's the very latest
When using the test bank account, I get this (not sure if "ach_credit_transfer" is correct here, but the documentation didn't provide clear guidance)
Okay that's weird.
I' still getting confused just a bit because the API ref docs use the type parameter: https://stripe.com/docs/api/sources/create
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
But I don't see that in any of the code snippets in the Connect doc
when using a test card (4242-4242-4242-4242), I'm getting this (even after refreshing multiple times to obtain new card tokens)
HI there 👋 I'm jumping in as my teammate needs to step away, please give me a moment to get caught up on the context of the thread.
Thanks - be nice if we could speak by phone
Could you copy/paste that most recent request ID here, and can you give me a high-level overview of what you're trying to build a flow to accomplish?
yes
grabbing that
this is the "invalid token" request id: req_cCzWColqqH6Gd5
here's the message about the email not being correct: req_2iY0ontHTHhq4z
In those requests, are you still trying to clone sources, or have you pivoted to just creating sources?
we're only trying to create sources
is this the wrong process?
this flow has been working for over 5 years, recently we upgraded from 5.36 to 20.116
Ah gotcha, the section of documentation that you linked to previously was for cloning sources from a platform to a connected account, but if you're just creating sources then that is different.
we're only trying to register new ACH and Credit Cards for users that register them. Again, this was working with our previous code without issue. No longer...
And when you say ACH, are you referring to ACH Credit Transfer, our previous version of ACH Direct Debit built on Sources, or our new version of ACH Direct Debit built on Payment Methods?
Just checking accounts - not sure the correct type is to choose for these...
with routing numbers and account numbers. to test, I was using the test account information from the stripe docs
Gotcha, so if you're collecting routing and account numbers then that is setting up ACH Debit. (ACH Credit Transfer spins up an intermediate account that customers can push funds to that you could then draw from).
Since sources and the old ACH debit flow are considered legacy at this point, the docs for them are a bit tricky to get to. Bear with me a moment while I get to those.
Here is the guide for ACH Debits on Sources:
https://stripe.com/docs/ach-deprecated
Regarding req_cCzWColqqH6Gd5:
You're seeing that error because the token that is being created is being created on your Platform, but when you try to reference that token you're making a request as your Connected account. Accounts are not permitted to access objects that belong to other accounts, so the request is failing. You'll need to create the token and source on the same account for this flow to work.
got it - so, could you point me to the definitive resource for handling the process for creating cards and checking account (ACH) sources under the latest API?
The above guide is the path for creating ACH debits on Sources.
And this guide walks through handling Cards via Sources:
https://stripe.com/docs/sources/cards
Correct, all of our Sources flow are considered legacy at this point. Our new recommended path is to build integrations on our Payment Method objects (rather than Sources) and to leverage Payment Intents (rather than Charges).
This migration guide helps explain the process of moving from our legacy flows to our newer ones:
https://stripe.com/docs/payments/payment-intents/migration
This page talks about our new ACH Debit Payment Method, and has links to guides that explain both how to accept a payment and how to save the payment method details to be used later:
https://stripe.com/docs/payments/ach-debit
And this document walks through our two recommended approaches for accepting payments in general (including, but not limited to, Card payments). These approaches support a wide range of payment methods, and the choices are either using a Checkout page that is Stripe-hosted, or embedding our Payment Element into your checkout flow.
https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout