question

The SDK you are using is for external point of sale systems that typically have their own concept of orders and do not use Clover orders. The SDK is not designed for use with Clover orders. Clover requires an order for all payments so Network Pay Display will create one for you behind the scenes when a payment is made. There is no way per my knowledge to suppress this or to associate an existing order via the SDK. So if you continue doing what you are doing you will end up with two orders.

You have a few options and there are complexities and pitfalls with each. I am not 100 percent either will work because I have never tried to build a kiosk app. Option 1 - you create the order and use the SDK you are using to launch a custom activity on the Clover device (the SDK has an API to do this). You pass the order id when you launch the activity and your app on the Android/clover device side uses the Clover Android payments API to create the payment (I think it has the capability to associate an existing order). Plenty of pitfalls here, you have to make sure the order has synced to the Clover device, you have to wire up all these moving pieces, you need an Android app to be approved and installed on the Clover device. Option 2 is a hack and I probably shouldn't even mention it. You do what you are doing now and you end up with two orders (not ideal) and you try using the rest API to create a payment record for the order you have created via the kiosk (check the rest API reference). This will be very odd, you will have to use an external tender and will have two orders and two payments. This won't be good for the merchants bookkeeping etc. A lot of things can go wrong here too. There may be some better options but that is all I can think of. Good luck.