#mrelliot69
low ice
HI 👋
What's up?
Sure, if you are using Server Driven Integration (our recommended path currently) then the API calls to process & capture the payment return synchronous results.
This is the overview of the server driven integration. If you want to see how it works in practice you want to start with this doc
https://stripe.com/docs/terminal/payments/connect-reader to review how to communicate with a reader from your POS
And then this doc to review how you collect payments: https://stripe.com/docs/terminal/payments/collect-payment
Correct. If you don't want to use webhooks you can poll the API and retrieve the Payment Intent directly https://stripe.com/docs/api/payment_intents/retrieve
Okay now I think we are missing one step. Server Driven integration requires manual funds capture. So when you call the process_payment API method it authorizes the payment but does not capture the funds. You make a separate API call to capture the funds and that will return synchronously a success or failure
Because if there is an error on collecting the payment method it will show up there. Like the errors we mention here: https://stripe.com/docs/terminal/references/testing#physical-test-cards
Card errors
Like if the bank declines the card
The processing step is the authorization with the issuing bank capturing the funds
Process payment confirms the Payment Intent, which includes getting authorization from the bank that issued the credit card to collect the funds.
After you have successfully being authorized to collect the funds you can capture them
I recommend you test this out and take a look at the status of the Payment Intent after each step. It will help you understand how it changes state based on the actions your POS takes.
what the manual property changes on the behaviour of this methods
This does not make sense to me. What are you asking here?
One immediately proceeds to capture the funds if the authorization is successful, the other waits for you to call the API to capture the funds
crude ermineBOT
low ice
I was able to poll the API near instantly with automatic capture and see the payment succeed.
You can test these API calls using our Simulated Reader
So you can be sure the API calls behave how you would expect
Bad WiFi connections will impact all API calls so it is something to consider
But I recommend using the simulated reader to get started