#dev-in-need_docs

1 messages · Page 1 of 1 (latest)

carmine fractalBOT
ashen ridgeBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

carmine fractalBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260324589310054461

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

proper wave
#

Hello
The doc you shared is for issuing cards with Stripe Connect.

It is different than an external account on a Connected account (which is used for payouts etc)

#

Can you share your exact usecase?

dense cliff
#

so I am building the stripe connect + issuing .

I am following the guide to fund the stripe issuing balance.

First I created a form for the user to enter in their bank account details - I then use that information to create the bank account token and create the source.

I am assuning when the source is created this sends off the microdeposits?

So now I need to display the bank accounts they have added and provide them the option to verify the account with the micro deposit values.

I Have the source id and the bank account id - I am just trying to determine what route to I call to retreive the bank account details and determin the status is new or verified etc?

proper wave
#

Gotcha. Are you using Pull Funding or Push Funding?

#

Sounds like Pull but just confirming

dense cliff
#

pull funding - microdeposit

proper wave
#

I am assuning when the source is created this sends off the microdeposits?
I believe so, yes..

So now I need to display the bank accounts they have added and provide them the option to verify the account with the micro deposit values.
What happens if you try to retrieve the source instead? What do you see as status ?

#

I don't think retrieveExternalAccount is the right method for this as the source isn't added as external account.

dense cliff
proper wave
#

The bank account object you linked is a different object than Bank Account Token -> Sources

#

The one you linked are for customer objects (not for issuing + connect usecase)

dense cliff
#

Ok I see. So the bank account token - creates a bank account - no? Where/how do I retrieve the bank account details?

proper wave
#

If you look at the banner in the docs, it calls out exactly the issue you're running into

Store these Source tokens in your own system where your integration can retrieve them. Stripe currently doesn’t provide a way to programmatically retrieve or list the tokens after they’re created.

Screenshot_2024-07-09_at_3.17.40_PM.png
dense cliff
#

no I know I do. But the source object doesnt have the bank accoutn verification status

#

so how do I retrieve the bank account verification status?

proper wave
#

Can you share the response object?

dense cliff
#

Source {
id: 'src_1Pak5RQ8nn4qito7ffVYvWXJ',
object: 'source',
ach_debit: {
bank_name: 'STRIPE TEST BANK',
country: 'US',
fingerprint: 'h1KlzTJu3LpDDGt7',
last4: '6789',
routing_number: '110000000',
type: 'company'
},
amount: null,
client_secret: 'src_client_secret_Cnf2Duye9BJqZW5kXS4xoKKU',
code_verification: { attempts_remaining: 3, status: 'pending' },
created: 1720554749,
currency: 'usd',
flow: 'code_verification',
livemode: false,
mandate: {
acceptance: {
date: 1720554749,
ip: '::1',
offline: null,
online: null,
status: 'accepted',
type: null,
user_agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36'
},
amount: null,
currency: null,
interval: 'variable',
notification_method: 'stripe_email',
reference: 'B8SVPAFGP5U7A5CN',
url: 'https://hooks.stripe.com/adapter/ach_debit/file/src_1Pak5RQ8nn4qito7ffVYvWXJ/src_client_secret_Cnf2Duye9BJqZW5kXS4xoKKU'
},
metadata: { verificationStarted: 'true' },
owner: {
address: {
city: 'Seattle',
country: 'US',
line1: '113 Cherry St',
line2: '',
postal_code: null,
state: 'WA'
},
email: 'caitlin@trytwig.io',
name: 'Twig Tech Inc.',
phone: null,
verified_address: null,
verified_email: null,
verified_name: null,
verified_phone: null
},
statement_descriptor: null,
status: 'pending',
type: 'ach_debit',
usage: 'reusable'
}

proper wave
#

I believe it moves to chargable status, meaning source has been verified

dense cliff
#

ok I see. thank you. I didnt realize the details were under the plaid tab instead of the microdeposit tab.

can you explain what these other status mean on a source?

The status of the source, one of canceled, chargeable, consumed, failed, or pending. Only chargeable sources can be used to create a charge.

proper wave
#

IIRC pending means the source isn't ready (hasn't been verified). Some sources are single use, so consumed means the source has been used for allowed number of times. failed and cancel could mean the verification failed so source can't be used. chargeable means it has been verified and is ready to be used.

dense cliff
#

got it - thank you very much