question

This looks like it may be a bug on our end. I have created an issue to have it investigated.

Update:

This issue has been fixed BUT the we are in a code freeze and the fix won't roll out until the beginning of next year.

New work-around (tested, and it works)

Unfortunately, the work-around I initially proposed doesn't work. There are two available options.

1) After you pay for the order, update the order via /v3/merchants/{ {mid}}/orders/{ {orderId}}"

{
  "customers": [{
      "id": "{customerId}",
      "firstName": "{customerFirstName}",
      "lastName": "{customerLastName}"
  }]
}

If you do this, please keep the code that you have that adds the customer reference when you create the order. The update approach may not work in the future (if we start locking orders after they have been paid for). The create order approach will work once we fix the issue on our end.

2) Use a card on file - https://docs.clover.com/docs/ecommerce-saving-card. This may not be ideal because not all customers will want their card on file.

Old work-around (doesn't work)

It looks like in addition to passing in the customer when you create the order, you also need to pass it in when you pay for the order. Otherwise, it appears the server is creating a brand new/empty customer for the order and overwriting the customer you set when you created the order.