From Nash Turcan (HeavyHaul Agent) to the Synchron CTO — route payments follow-up — October 6, 2026, 2:41 PM ET
Asked by: Nash Turcan, HeavyHaul Agent (HHA). To be answered by: the Synchron CTO and development team. This replies to "Synchron answers to the HHA follow-up questions" of October 6, 2026. Part 1 gives Nash's decisions on the six open points. Part 2 asks Synchron 11 new questions, with a column for the answers. Part 3 answers Synchron's 24 questions to HHA; items marked "HHA to confirm" will follow.
Part 1 — Nash's decisions on the six open points
- One trip, several companies. A Synchron order concerns the carrier only. HHA sends the carrier, the carrier-side dispatcher or user making the purchase as the client, and the driver when one is known. HHA never sends broker, pilot car or other unrelated companies, so an order must never be blocked because other companies share the HHA trip.
- GPX and Hummer files. They stay in HHA's Express Route description. Synchron generates the Google Maps route and sends it through the existing API flow to the HHA Factory, which generates the GPX file and the Hummer GPS link. Synchron does not need to produce either.
- Express routes not released at once. HHA shows the route as "Processing" or "Being prepared" until it is delivered. A route that was not released automatically is never shown as an error.
- Required carrier, driver, truck and trailer fields. For permit purchases, carrier, truck and trailer are mandatory, and HHA will require them before a permit order. For route purchases, HHA sends the real carrier, truck, trailer and driver data it has learned from the trip and its permits. When a field Synchron technically requires is genuinely unknown, HHA sends a placeholder: 1111 for a number, XXXXX for text. Placeholders are a fallback only.
- CVV re-entry versus saved card plus 3-D Secure. Saved card plus 3-D Secure is acceptable, provided the Synchron CTO confirms it creates no meaningful security, payment-compliance or customer-protection issue. Please document why the CVV page was declined, and raise any material reason for an extra confirmation step before implementation.
- HHA address for callbacks and Checkout returns. Use heavyhaulagent.com. HHA will send the exact paths with the staging details.
Part 2 — Questions for the Synchron CTO
Asked by Nash Turcan (HHA). To be answered by the Synchron CTO.
| # | Question | Synchron answer |
|---|---|---|
| 1 | Purchaser outside the carrier. The order belongs to the carrier. When the person buying is not a carrier user (a broker on the trip, or an HHA admin), who should be the client on the order? Can HHA send the carrier with the buying user as client, whatever their company? | |
| 2 | Carrier changed after a purchase. A load can be reassigned to another carrier after a route was bought. Will the next purchase on that trip number get a 409 conflict? Should Synchron update the order's carrier, or keep one order per carrier? | |
| 3 | Placeholder values. Nash allows 1111 for unknown numbers and XXXXX for unknown text on route purchases. Can the request mark which fields are placeholders, so staff and reports never treat them as real? Separately, HHA's permit reading returns a permit weight of 1,111 lbs on many permits. Do Synchron orders or permits carry 1111 as a placeholder weight today? | |
| 4 | Routes reaching the HHA Factory. Today the existing API flow sends the Google Maps route to the HHA Factory, which makes the GPX file and Hummer link. For purchased routes, will that flow keep running next to route.completed, so every purchased route also gets GPX and Hummer? Which call carries it? | |
| 5 | Saved card without CVV. Please confirm in writing that charging a saved card off-session, with 3-D Secure only when the bank asks, raises no security, card-network compliance or customer-protection issue. Please also document why the CVV page was declined. | |
| 6 | Mandatory fields for permit orders. Which carrier, truck, trailer and driver fields are mandatory on Synchron's side for a permit order? HHA will require exactly those before a customer can order. | |
| 7 | Driver data. When a driver is known, which fields should HHA send (name, phone, email, license number)? | |
| 8 | Start date and staging address. Your answers leave the start date and the staging URL to be set. When do you start, and what is the staging URL? | |
| 9 | Trip number ranges. HHA proposes staging 100000000–199999999 and production 200000000–999999999. Do you agree? | |
| 10 | Imported orders without permits. 21 imported orders have no permits, for example 93939530 and 21810243. Do they really have none? | |
| 11 | Imported permits without maps. 20 imported permits are marked "needs preparation" and have no map, for example the IL permit on order 38762483. Will they get maps, and how is HHA told? |
Part 3 — HHA's answers to Synchron's questions
Asked by the Synchron CTO. Answered by Nash Turcan (HHA). Numbered by section as on Synchron's page.
Trips, users and order data
| # | Synchron's question | HHA answer | Status |
|---|---|---|---|
| 1 | Trip numbers: always 9 digits, first digit 1–9, sent as text, never reused? | Yes. HHA shows HH-512048337 and sends "512048337" as text. Before going live HHA will keep a permanent register of issued numbers, so a number is never reused, even after a trip is deleted. Trips imported from Synchron keep their 8-digit order token; their routes are included and never bought. | Answered |
| 2 | Separate number ranges for staging and production? | Proposed in Part 2, question 9. | Awaiting Synchron |
| 3 | Can dispatchers of the same company buy on one trip? A stable company ID? | Yes. HHA sends one company per purchase: the trip's carrier, with a permanent HHA company ID. The client is the carrier-side user who buys, and the driver is sent when known. Broker and pilot companies are never sent. | Answered |
| 4 | How should HHA handle a 409 trip number conflict, and who is alerted? | HHA stops the purchase, tells the customer it could not start, logs it and emails the HHA admin. | HHA to confirm the alert address |
| 5 | Can HHA always send truck and trailer VINs, DOT and MC? | For permit purchases, yes: HHA will require carrier, truck and trailer data before an order. For route purchases, HHA sends the real data learned from the trip and its permits. When a required value is unknown, HHA sends 1111 for a number or XXXXX for text (see Part 2, question 3). | Answered |
| 6 | Does HHA verify email before purchase? Is the HHA user ID permanent? | Accounts created with an email code or Google have a verified email; HHA sends email_verified true only then. The user ID is HHA's permanent profile ID. | Answered |
| 7 | The trip data schema for Buy More Permits? | HHA can send origin, destination, commodity, dates, load and overall dimensions and weight, truck and trailer details, trailer axle count, driver contact and existing permits. HHA does not record axle spacing or axle weights today. A full schema follows when permit ordering starts, after route purchase. | Answered |
Routes, pricing, credits and refunds
| # | Synchron's question | HHA answer | Status |
|---|---|---|---|
| Routes 1 | Is the route token the same one sent to /ai/v1/permittoken? Should the purchase itself start the routing work? | The HHA web app never calls Synchron directly; HHA's agent backend does when it reads permits, and the token on HHA permits is the one it returns. HHA proposes that the purchase itself starts the routing work. | HHA backend to confirm |
| Routes 2 | Does HHA need GPX and Hummer files? | Yes, but Synchron does not make them. Synchron sends the Google Maps route through the existing API flow to the HHA Factory, which generates the GPX file and the Hummer link. See Part 2, question 4. | Answered |
| Routes 3 | What does /api/auto_approval do, and when can HHA switch to route.completed? | That endpoint belongs to HHA's agent backend, not the web app. HHA can receive route.completed once both sides finish route purchase. | HHA backend to confirm |
| Routes 4 | Express sent to the manual queue: is 30–60 minutes acceptable? | Yes. HHA shows the route as "Processing" or "Being prepared" until it is delivered, never as an error. | Answered |
| Pricing 1 | A $100 maximum per route, and always USD? | Always USD: HHA prices are $1.99 and $10.00, stored in US cents. | HHA to confirm the $100 maximum |
| Pricing 2 | What is a credit reference? Does HHA return the credit on refund? | A credit route is recorded in HHA as a route request paid with a credit, and that request's ID is the reference. On purchase.refunded HHA cancels the request, which returns the credit. | Answered |
| Pricing 3 | In a mixed cart, does HHA hold credits until payment? | HHA never mixes them: a credit is spent from the permit's own button, and the cart takes card payments only. An abandoned checkout can never use a credit. | Answered |
| Pricing 4 | Do customers ask HHA or Synchron for refunds? | Proposed: customers ask HHA support, and HHA passes the request to Synchron staff. No refund endpoint for the first version. | HHA to confirm |
| Pricing 5 | Statements show Synchron's name; should Checkout mention HHA? | Proposed: yes. Checkout names "HeavyHaul Agent route purchase", and the card statement shows a suffix such as "HHA ROUTES". | HHA to confirm |
Callbacks, security, documents and testing
| # | Synchron's question | HHA answer | Status |
|---|---|---|---|
| Callbacks 1 | One callback URL, or one per event? | One URL for all events, on heavyhaulagent.com. HHA sends the exact path with the staging details. | Answered |
| Callbacks 2 | Do HHA servers keep their clocks in sync? | HHA will confirm with its host that time sync is on. | HHA to confirm |
| Callbacks 3 | Every Synchron endpoint HHA calls, and with which key? Does HHA call the open order endpoints? | HHA's import scripts call /api/v1/carriers/relations, /api/v1/carriers/{id}/full-records and /api/v1/orders/full-records with HHA's API key; they need carriers:read and orders:read. The HHA web app calls none. Neither open order endpoint is used by them. HHA's agent backend will list its own calls. | HHA backend to add its list |
| Callbacks 4 | Is the token Synchron uses to call HHA the hardcoded one? Who issues the new one? Does FRONTDESK_API_TOKEN need rotating? | Those calls (auto-order, ext-ratecon, update-order, auto_approval) reach HHA's agent backend. The backend developer issues the new token and confirms the old one is revoked. | HHA backend to confirm |
| Callbacks 5 | 3-D Secure links: shown in HHA, emailed by Synchron, or both? | Proposed: both. HHA shows the link on the trip, and Synchron emails it to the cardholder. | HHA to confirm |
| Documents 1 | Storage domains, SHA-256 and 24-hour links? | HHA documents are in an Amazon S3 bucket; a few older ones are in Supabase storage. Links for Synchron will last 24 hours, and each file comes with its SHA-256. HHA sends the exact domains with the staging details. | Answered |
| Documents 2 | Expected volume per day and per minute? | Low: tens of route purchases a day at first, far below 60 requests a minute. | Answered |
| Documents 3 | HHA staging URL, test start date and contacts? | HHA is setting up a staging environment and will send its URL and the technical contacts. Testing can start once Synchron's staging is ready. | HHA to confirm |