Attaching CloverGo payment to existing orderID

Question

question

bennetbrauer85 asked Nov 26, '19 David Marginian Deactivated edited Dec 2, '19

Attaching CloverGo payment to existing orderID

Is there a way to apply a payment from the Clover Go to an existing order in the merchant's PoS?

We're building a iPad based semi-integration and we've been working with the CloverGo iOS example app (https://github.com/clover/remote-pay-ios-go) which has been working fine. However, the example only illustrates creating a new order and adding a custom item. Per this snippet from the CloverGoConnector Swift file....

Can someone please point me to documentation or an example of how to attach a CloverGo payment to an existing order?

Orders PaymentConnector Clover Go

1574797872206.png (432.4 KiB)

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community

Answer 1 · 2019-11-26T20:34:06Z

Jeffrey Blattman answered Nov 26, '19 David Marginian Deactivated edited Dec 2, '19

All payments are attached to orders, whether the app in question exposes that detail or not. You should be able to retrieve the payment, then check the order ID attribute.

If you are asking how to move a payment from one order to another, that is not possible.

4

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

bennetbrauer85 commented · Dec 01, 2019 at 05:05 PM

Thanks for the response Jeffrey. We’re trying to open an order through the v3 API and use the CloverGo to process a payment and close out the order. Is this possible?

The CloverGo iOS example I linked to only creates new orders for the payments from CloverGo, no option to pass in an existing orderID.

0 ·

David Marginian ♦♦ bennetbrauer85 commented · Dec 01, 2019 at 09:04 PM

I don't think this is currently possible (although I don't know much about the Go SDK). In general semi-integrations assume that the POS owns the order. The SDK creates the Clover order because it is required for a payment but it is only an internal place-holder to get around the requirement.

0 ·

bennetbrauer85 David Marginian ♦♦ commented · Dec 02, 2019 at 03:00 PM

David/Jeffrey,

Appreciate your responses on this! Are you able to confirm with the semi-integrations team or someone internally regarding this? I've emailed them but no response.

In this code snippet from the sample app...

it shows the "keyedRequest" function requires an order for the payment (like you two have mentioned, which makes sense) but it would seem that we could use the CloverConnector SDK to retrieve an existing order and pass THAT order in for the payment versus creating an entirely new order.

Anyone you could reach out to, put me in touch with or even documentation you could point me to would be GREATLY appreciated.

0 ·

screen-shot-2019-12-02-at-95439-am.png (100.2 KiB)

Show more comments

question