#don-issuing-capabilities

1 messages · Page 1 of 1 (latest)

sturdy sequoiaBOT
peak ravine
#

don-issuing-capabilities

#

Hey @patent stream! Can you give me real data like the request id? It's the req_123456 in the request_log_url property you redacted.
Also if you have 30 years of coding experience, you should be able to quickly write real code locally with your live API key instead of messing with the CLI in live mode (you can do the CLI if you want, just less ergonomic especially for production changes)

patent stream
#

I am sure I will - CLI was the first way in I found (Stripe documentation is not very clear/step-by-step so I started with googling). Request info I think you need: req_0ptdSqgXMPtV5a?t=1674847083. I am being careful not to share too much real data - hope this is what you need?>

peak ravine
#

Try real code then. Any of the other languages, just not the CLI

patent stream
#

I would like help with the CLI approach first - can you help with that?

peak ravine
#

Yes I can help by telling you not to do that, it won't work for that specific case

patent stream
#

OK how do I write code locally (starting from the dashboard)

peak ravine
#

Sorry, you mentioned you have 30 years of experience as a developer

patent stream
#

Yes and I also said I am new to stripe

peak ravine
#

Are you the developer integrating Stripe? Because you can't really use Custom + Connect + Issuing without having already written real code

patent stream
#

At this point I simply want to add the capability 'issuing' to the account. My understanding is the dashboard doesn't have the option to set that (yet) so simple API code is needed. The only code I have written for stripe is this code (I started yesterday)

peak ravine
#

okay so if you started yesterday, you shouldn't be doing any of this in production in any way

#

Never use real accounts, real money, real keys etc.

patent stream
#

I want to set up virtual cards and my understanding is I need the issuing capability

#

Let me manage the risk - I am just looking for help on the how

peak ravine
#

Step 1: Choose a programming language you plan to build your integration in
Step 2: Read https://stripe.com/docs/issuing/connect and follow the instructions on how to create an account with all the right information with code upfront

If you don't want to do that, that's fine, but we also won't help you here

#

Ultimately right now the CLI can not perform that specific operation of changing the capability on an account. So you will have to either switch to curl + your API key, or write real code in your preferred language. If you aren't familiar with Stripe at all, the first step would be to follow https://stripe.com/docs/development/quickstart and play with the API first

patent stream
#

I have already been through that help and the following is what I am trying to do (from that) Each business entity that uses issued cards must be represented by a Custom connected account. Create a new Account with the following capabilities:

card_issuing
transfers
card_payments