#ticket-terminal-serverdriven
dire pollen
Hello 👋
Not sure I completely follow. If the capture method is set to automatic then the payment would be captured immediately after confirmation.
Can you elaborate on what you're trying to do exactly?
lone sigil
sure
with our current payment processor when we process payments transactions move from Authorized -> settling -> settled
when they are in a settling state, we are able to void (cancel) payments. Once it is settled, we cannot void (cancel) payments, we have to refund.
our development team is wondering if CaptureMethod=automatic, would this transaction be considered as "settled" and therefore not available for void.
dire pollen
I see. My understanding is that with capture method automatic, the payment would be captured as soon as it is confirmed. After that, the only way to release the funds back is to create a refund
lone sigil
okay thank you for clarifying
I also have another question
for server-side integration, According to documentation When you successfully process a payment, the returned object contains a successful charge ID. This charge contains a generated_card ID, which represents the ID of a card PaymentMethod that’s used to charge the saved card.
But service.ProcessPaymentIntent("tmr_xxx", options); method returns Reader object which does not contain Charge info. Where cacan we get this info from?
dire pollen
Can you share the docs you're looking at?
lone sigil
can you confirm that this function is available in Australia as well please. I notice the documentation only specifies this functionality is available in the US but we would like to have it in both countries, if possible.
dire pollen
That's US only unfortunately.
SetupIntents are supported in australia
https://stripe.com/docs/terminal/features/saving-cards/save-cards-directly
for server-side integration, According to documentation When you successfully process a payment, the returned object contains a successful charge ID. This charge contains a generated_card ID, which represents the ID of a card PaymentMethod that’s used to charge the saved card.
Can you share the test charge IDs you're working with?
lone sigil
we are still in discovery and have not began development yet.. so we have not run any test charges at this point.
dire pollen
I see. Also, I don't believe server-driven SDK supports saving card details after the payment flow
https://stripe.com/docs/terminal/features/saving-cards/save-after-payment
Its limited to JS, iOS, Android and ReactNative
hexed hollyBOT
dire pollen
I haven't tried it myself with SDI though so not sure 100%
You'd likely want to play around with it
You should see the successful charge ID on the PaymentIntent which you can retrieve by listening to webhooks
lone sigil
Okay. We will still be able to get the card info (card type, first 6 digits & last 4 digits, name on card, etc) using the server driven integration, correct?
dire pollen
It often depends on the way of payment method collection.
Like Tap vs Insert vs Swipe may produce diff results
That's regardless of the SDK though
hexed hollyBOT
twin mantle
ticket-terminal-serverdriven