#ahsan-terminal-directcharges
tame mesa
green heron
@gilded wave have you seen https://stripe.com/docs/terminal/features/connect#direct?
ahsan-terminal-directcharges
gilded wave
Thanks for the quick response. I actually read that article so the issue in my case is I have the API setup for my account and it is working fine...
I have the stripe connected account on my main account. Now I want to create a Simulated BBPOS WisePOS E test reader on that connected account so that ....
green heron
Okay so what is the problem? What does your code look like, what isn't working, what errors do you get, etc.
gilded wave
ok I have one test terminal reader on my main account like this one... Now I want to create the exact same stripe terminal reader for testing purposes on one of my connected accounts... When I go to the connect account dashboard it does not display any options to create a new terminal reader. Like under connect->stripe terminal, I can not create a new reader
green heron
You should use the API for this no? like https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=server-driven&reader-type=simulated#create-a-simulated-reader
gilded wave
Yeah I suppose I can do that... but for real customers who have actually purchased the stripe terminal and want to integrate the payment, will the apis work the same way for them as well ?
Like I used to process the payments on terminal like this
$stripe->terminal->readers->processPaymentIntent(
$request->stripeReaderId,
['payment_intent' => $request->paymentIntentId]
);
so, if the customer has multiple terminals then they can select any one from a frop down and from there I will get the terminal id to process the payment
green heron
it works similarly but you have to change your code. All your calls will be made on the connected account so you have to use the Stripe-Account header option as documented in the link I shared earlier or https://stripe.com/docs/connect/authentication#stripe-account-header
gilded wave
yeah I do this instead of that
$stripe = new \Stripe\StripeClient(['api_key' => STRIPE_API_KEY, 'stripe_account' => $request->accountId]);
I checked the stripe library code and they were getting the additional parameter while initializing the object
so now every request on this object will be made on that specific connected account...
green heron
yep that's correct!
gilded wave
But I was so sure of creating a terminal reader on standard connected account dashboard... instead of creating one through API... but will give it a try. thanks.
Could it be because my standard connect account is in test mode ?
green heron
As a platform you can't really do most things in the Dashboard for Standard accounts. So API is the right way
gilded wave
ok cool. thanks a lot for all the help... appreciate it