HTTP Tracker API visit id


We are trying to inject an eCommerce transaction into an existing visit. It matches the visitor, but creates a new visit, and all subsequent transactions end up in that visit. Is there a way to specify which idVisit this HTTP action should be inserted into?

I feel like we might not be matching the config_id of the Visit 5, so it keeps inserting into Visit 4, any thoughts?

The API call shows:
The visitor is known (idvisitor = d95a5b7f86554238,
DEBUG: config_id = 0d523042d354ee83,

DEBUG: The visit is part of an existing visit