#12345 - In Person Payments
fresh depot
No worries.
mystic sedge
Okay you're talking about the capture step that occurs after collecting payment details through the Terminal device?
fresh depot
correct, where the in-person payment quickstart says:
You must manually capture payments processed by the Terminal SDKs. Set up your backend to capture the payment within two days. Otherwise, the authorization expires and funds get released back to the customer.
mystic sedge
The preferred method is to capture the funds as quickly as possible. This prevents the user from seeing only a "Pending" charge on their account. As the docs state you can delay up to 2 days but that's really not a great user experience.
fresh depot
I see, and in the event that the client has disconnected before initiating the capture, it's probably better that it stays uncaptured for the time being... so having a webhook automatically capturing everything it can wouldn't make much sense?
I guess it depends on the specific use-case, but I'm trying to avoid a situation where we "forget" to capture a payment. but as long as we don't consider an order/sale (on our end) to be completed until after we've received an OK response on the request to capture a payment it should be fine?
mystic sedge
That depends on which process makes the most sense for the product/service you are providing.
Even if your client disconnects from the reader I don't see why that should impact the capture step since that does not involve communicating with the Terminal device
fresh depot
I was more concerned about the client disconnecting from our backend service, or from the internet entirely. But in that case it probably makes sense to not capture the payment until the client is back online and we can complete the order properly.
Anyway I think it's clear enough now, you can close this and I'll ask again if I have further questions 🙂 Have a good day!
mystic sedge
I'm glad we could get you some clarity 🙂 I hope all goes well and the internet remains stable