Node.js & PostgreSQL Backend Developer — Complete & Launch Logistics Platform (Stripe, Twilio)

Backend Node.js Developer — Production Logistics Platform We operate a live same-day courier and logistics platform. The backend is a production-grade Node.js/Express application with PostgreSQL, fully integrated with Stripe, AWS S3, Twilio, Shipday, and Checkr. The codebase is clean, modular, thoroughly documented, and has passed multiple independent technical audits. You are not starting from scratch. The platform is approximately 85% complete. What remains is a defined set of endpoints, a complete catering pricing engine, a WordPress site migration, and a production deployment — all fully specified in writing before you start. What Is Already Built • Stripe Authorize + Capture payment flow and Stripe Connect driver payouts • Driver onboarding — multi-step flow from application to activation • Admin console — orders, drivers, customers, invoices, business leads, discount codes, contract rates, and revenue/driver reporting, all with role-based access control and full audit logging • Pricing engine — 11 industry rate tiers, multi-track routing, surcharges, fully built pallet pricing engine with two-track weight-based calculation • Per-customer contract rate override system • Business lead management and lead-to-customer conversion • Checkr background check integration with FCRA adverse action support • AWS S3 document storage with signed URL retrieval • Twilio SMS + email notifications — majority already wired and firing • Shipday dispatch webhook integration • PostgreSQL schema with 29 tables, migrations, seed data, and cargo reference data • Invoice Reminder & Payment Terms System — automatic overdue-invoice reminder sequence via SMS or email based on customer consent, admin escalation alert, support for Net 15/30/60 and due-on-receipt terms — built and tested What We Have Already Done For You We believe in setting our developers up for success. Before this job was posted, we did the heavy lifting so you can hit the ground running with the least amount of friction possible. API Key Assignment & B2B Order Intake (Section 14) The complete enterprise client integration layer is written and ready: API key generation and authentication middleware, inbound order endpoint, order status endpoint, webhook delivery with HMAC-SHA256 signing, per-key rate limiting, and full admin key management. You wire it in — four files, three lines in app.js, one migration. Admin Console A fully built admin console — role-based access control, full audit logging, and everything an operations team needs to run the platform day to day. It is built, tested, and waiting. Staff Training Portal (Section 16) The complete in-house personnel training system is written and ready: seven endpoints covering module delivery, signed video URLs, forward-only progress tracking, quiz grading with incorrect answer explanations, attestation, Puppeteer certificate generation, and role-based module filtering. All five new database tables are defined, constrained, indexed, and seeded. You wire it in alongside Section 14. Driver Payout System The complete manual weekly driver payout system is written and ready: pre-payout summary report with per-driver order breakdown and integrity check, batch Stripe Connect transfer initiation, per-order payout override, dispatch release gate that locks the payout amount before it reaches the driver, 7-day dispute window, 7-year record retention enforced at the database level, IRS $600 threshold notification, and full earnings search by driver name, phone number, or order number with CSV and PDF export. Payments — Stripe Authorize + Capture, driver payouts via Stripe Connect, webhook handling with signature verification — built. Driver Onboarding — Complete multi-step flow from application through background check, training, agreements, and activation — built. Pricing Engine — 11 industry rate tiers, multi-track routing, after-hours surcharges, pallet pricing, and per-customer contract rate overrides — built. Notifications — SMS and email via Twilio and Nodemailer, majority already wired and firing — built. Third-Party Integrations — Checkr for background checks, Shipday for dispatch, AWS S3 for document storage — all integrated and working. All pre-built sections include a step-by-step integration guide, full acceptance tests, and clear documentation of what is pre-built versus what remains your responsibility. The codebase you receive is clean, modular, and has passed multiple independent audits. You are not inheriting someone else's mess — you are inheriting a head start. What Needs to Be Built • Booking confirmation endpoint — wires the existing authorizePayment service to a fully transactional HTTP endpoint • Customer authentication system — accounts, saved addresses, order history • Quick quote estimate endpoint • Driver background check payment step • Admin document upload endpoint • Detention records endpoints • SMS consent field on the customer booking form — required Yes/No selection at intake, feeds the Invoice Reminder System's channel logic • Admin console screen for manual invoice creation (backend endpoint already built) • PHI training module — following the existing PII training pattern • Wire five remaining notification functions to their triggers • Invoice email status tracking • Driver portal for PII/PHI training access • Multi-stop dynamic booking — multiple pickup and dropoff addresses with Google Maps route calculation and Shipday multi-stop integration • A complete catering pricing engine — headcount-based pricing, invoice verification, and a 5-layer anti-split detection system — fully specified in a separate detailed document provided to the selected candidate • A complete platform documentation booklet written in plain English — covering every feature, every admin function, environment setup, troubleshooting, and maintenance — required deliverable before payment • 39 platform enhancement items — fully specified in the codebase • WordPress site migration — take handoff from the WordPress developer, wire the booking form to the platform API, verify all systems on staging, execute the domain swap, and confirm everything is live and working Note: the WordPress front-end site is currently under separate development and is not yet ready for integration. The backend developer's WordPress-migration and form-wiring tasks — booking form, business registration, driver sign-up, and B2B API docs verification — begin only once front-end work is complete. Timeline for that handoff will be communicated once the candidate is selected. • WordPress site migration — take handoff from the WordPress developer, wire the booking form to the platform API, verify all systems on staging, execute the domain swap, and confirm everything is live and working Tech Stack Node.js 18+ · Express · PostgreSQL 15+ (raw SQL) · Stripe v14 · AWS S3 · Twilio · Checkr · Shipday · Google Maps API · Zod · JWT · Docker · PM2 What We Are Looking For • Strong Node.js and PostgreSQL — you read and extend a production codebase without rewriting what already works • Stripe PaymentIntents, Authorize + Capture, and webhook handling — real production experience, not tutorial-level familiarity • Experience with idempotent webhook processing and transactional database operations under concurrent load • Google Maps API — multi-stop route and distance calculation • AWS S3 — signed URLs, secure file upload and retrieval • Security mindset — PII handling, FCRA awareness, role-based access control • Documentation discipline — every addition must match the existing standard of in-code comments and API reference documentation • Full ownership mentality — you are responsible for the entire backend platform from build through production deployment, not selected pieces of it • WordPress site migration experience — staging to live domain swap, URL structure preservation, zero downtime, plugin migration with all settings intact • DNS verification — MX, SPF, DKIM records confirmed intact after migration • Email verification — all six company email addresses confirmed receiving and sending correctly before go-live • Full integration verification on staging — Shipday, Twilio, Stripe, and Checkr all confirmed working before anything goes live • B2B API preservation — api.motionmileslogistics.com/v1/docs must remain fully intact and accessible after the WordPress migration. This is a separate Cloudways application and must not be affected by the domain swap. Existing enterprise client API keys must continue authenticating correctly. How Payment Works This is a single fixed-price engagement — get it done, get paid. There are no milestone splits and no partial payments. • The full $800 is funded into Upwork escrow before work begins. The funds are secured and visible to you from day one. • Payment is released only after the complete platform — every endpoint, the catering engine, multi-stop booking, WordPress migration, and full production deployment — has been thoroughly tested and verified working by you against a detailed acceptance checklist provided in the developer brief. You test it yourself before handing it over — this is not a project where the client debugs your work for you. • All work is done in a staging environment first. Nothing goes live until reviewed and approved. • The backend developer owns the complete staging to live migration — domain swap, DNS verification, email verification, and full system confirmation across Stripe, Shipday, Twilio, and Checkr. The client does not press any buttons. Nothing goes live until every system is verified working on staging first. • All communication and payment happens through Upwork only. No payments outside the Upwork escrow system under any circumstances. • No phone calls. No Zoom meetings. No exceptions. Every conversation, every decision, and every instruction must be documented in the Upwork chat. If it was not written in the chat, it did not happen. 30-Day Post-Launch Warranty Once the platform is live in production, the developer provides 30 days of warranty support at no additional cost. This covers: • Bug fixes for any issue arising from work completed under this contract • Resolving any integration failures — Stripe, Checkr, Shipday, Twilio, AWS — tied to the original build • Addressing any production issue that was not caught during testing • Email deliverability issues arising from the migration This warranty period does not cover new feature requests or scope changes — only the correct functioning of what was built and deployed under this contract. The One Rule Every new endpoint must be documented in the same standard as the existing codebase — full request/response shapes, error codes, and role requirements in the API reference, with the Postman collection updated accordingly. Undocumented work will not be accepted for payment release. GitHub — Non-Negotiable All work must be committed to the provided GitHub repository throughout the engagement. This is not optional and is not a final step — it is ongoing from day one. • Every change must be committed with a clear, descriptive commit message • The repository must reflect the current state of the codebase at all times • Commits must be logical and incremental — not one massive commit at the end • You do not submit work by sending files — you submit work by pushing to the repository A clean, readable commit history is part of the deliverable. Work that cannot be reviewed in GitHub will not be accepted for payment release. Fixed price only. No hourly billing. The amount reflects the remaining scope — integration, completion, migration, and deployment of a platform where the heavy lifting has already been done. Successful completion opens the door to an ongoing retainer for platform maintenance and future feature development. To Apply Tell us briefly about a Stripe PaymentIntent or webhook integration you have built in production — specifically one that involved Authorize + Capture or Stripe Connect. Also mention your experience with full WordPress site migrations — staging to live domain swaps where URL structure and plugin configurations had to be preserved exactly. Generic applications will not be considered.