Clear answers before you move cargo.

Releases are milestone-based and GPS-triggered:

• 40% release — triggered on GPS pickup confirmation, same business day
• 60% release — triggered on GPS delivery confirmation, same business day

Admin reviews each withdrawal request before approving the release instruction to the bank. The bank verifies every instruction at btsh.africa/verify before processing.

The Shipper does not pay Paystack directly into BtSh. The flow is:

• Shipper clicks Top Up on their dashboard
• BtSh opens the bank's payment interface
• Shipper completes the bank transfer
• Payment lands in the BtSh Freight Escrow account
• Bank automatically credits the Shipper's BtSh wallet balance
• Shipper uses wallet balance to Fund Load

Yes. BtSh Connect exposes standard HTTPS APIs and webhooks so an enterprise integration team can connect SAP, Oracle, Microsoft Dynamics, a TMS/WMS or a custom internal platform. The enterprise system remains responsible for its own internal workflow; BtSh becomes the freight-execution interface.

No. This is an important distinction.

• 500 independent shipments: your ERP can call the normal Loads API once per shipment.
• BtSh Repeat Route or Multi-Destination workflow: use the Bulk Loads API.

Your team may select hundreds of shipment rows inside its ERP and click an action such as Send to BtSh. The integration then submits those shipments independently, subject to the company's approved rate limits.

Through BtSh webhooks. Your company registers an HTTPS endpoint and subscribes to the event families it needs. BtSh then pushes lifecycle events back to your system as the freight operation changes.

• load.* — load creation and lifecycle status
• trip.* — Trip Master and geofence-related events
• document.* — available operational documents such as POD
• invoice.* / payment.* — supported finance-related events

Your ERP should store the BtSh event ID and process webhook events idempotently so a retried delivery does not duplicate the business action.

Sandbox is for integration testing. It uses real BtSh Connect authentication, scopes, idempotency and payload rules, but sandbox write operations remain isolated from production loads and real money.

Production is the live environment. Approved production credentials can create real BtSh business records and enter the normal corporate approval, General Market, matching, escrow, Trip Master, confirmations and finance lifecycle.

BtSh's trip and geofence mechanisms need more than an ambiguous typed address. Enterprise load creation therefore uses geofence-grade location information: formatted address, Google Place identity and latitude/longitude.

No. A corporate account is an organisation-owned workspace. It can support authorised members, internal departments/business units, enterprise roles and controlled access while the organisation remains the owner of its freight records.

• Primary Administrator controls the corporate workspace
• Finance-level users can receive the appropriate financial access
• Operational members can work inside their authorised business context
• Corporate ownership and internal references remain attached to company loads

This avoids forcing a large organisation to treat one employee's personal login as the company's permanent logistics identity.

No. Corporate workspace access and BtSh Connect access are controlled separately. A company may request integration access, and BtSh Admin can provision the appropriate API products, scopes, sandbox access and—after readiness/approval—Production access.

Enterprise access is not created through the ordinary public registration form. Submit the Enterprise Access request form with your company, authorised contact, approximate freight volume, current system and intended use case.

BtSh Admin reviews the request, contacts your organisation and then provisions the corporate account and any required BtSh Connect access through controlled onboarding.

No. BtSh deliberately does not reveal the Carrier's identity — including company name, truck plate, or driver details — to the Shipper on the platform. The Shipper's assurance of quality is BtSh's verification system: every Carrier and Driver is KYC-approved and Admin-verified before assignment.

Yes. The Shipper sees the trip through Trip Master, including driver movement, progress, ETA, route behavior and milestone updates when live GPS is active. Every confirmed milestone is permanently logged and verifiable at btsh.africa/verify.

The Shipper posts a base freight price with the load. The Dispatcher takes that price to their Carrier network and negotiates — going back and forth between both parties — until a final number is agreed. The Dispatcher then sets the agreed price on the platform, locking it for that load.

No. Dispatchers never handle Shipper money. Coordination happens entirely on the platform. The Shipper pays to escrow, and release instructions are generated only through verified GPS milestone actions. Dispatcher commissions are credited to their wallet by BtSh after each completed load.

Yes. Admin can force assign a load when there are unnecessary delays, poor coordination, or when load progress is at risk. This is a platform governance tool — not a routine action.

No. Carriers do not browse loads or bid. They are assigned to loads by Dispatchers who select a verified truck and driver from the Carrier's approved fleet. This is a deliberate design choice — it ensures every assignment is coordinated, verified, and structured.

Carrier payment is guaranteed and milestone-triggered:

• 40% of net freight — same business day as GPS pickup confirmation
• 60% of net freight — same business day as GPS delivery confirmation

Deductions from the Carrier's freight include the 8% Dispatcher commission and 2% platform fee.

A Driver Session Token is a one-time, load-specific access credential generated by the Carrier on their dashboard. It looks like: DS-BTSH-12NBXXX.

• Tied to one specific load, truck, and driver — cannot be reused
• Expires when the load status reaches DELIVERED
• Can be invalidated and regenerated by the Carrier if needed
• Every token use is logged with timestamp and device information

The Driver confirms two GPS milestones:

• Pickup confirmation — when cargo is loaded and the truck departs the pickup address. This triggers the 40% payment to the Carrier.
• Delivery confirmation — when cargo arrives at the delivery address and is handed over. This triggers the final 60% payment.

GPS coordinates and timestamps are permanently recorded for both confirmations and cannot be altered.

PMs earn through two streams:

• Truck Onboarding Fee — a fixed fee per verified Carrier (truck owner) successfully onboarded using the PM's referral token
• Load Commission — 10% of BtSh's Platform Fee on every completed load by a Shipper referred by the PM

Partner Managers have strict limits:

• Cannot collect money, fees, or any payment from Shippers or Carriers on behalf of BtSh
• Cannot claim to be a BtSh employee, agent, or representative
• Cannot use BtSh's name or logo without prior written approval
• Cannot share their PM token with another person
• Cannot make earnings guarantees beyond what is published in official BtSh materials

Any violation may result in immediate termination of PM programme access.

Trip Master shows:

• Live driver location on map
• Route progress and distance covered
• Estimated time to delivery
• Load reference and current status
• GPS pickup and delivery milestone timestamps
• Session status — Active, Pickup Confirmed, Delivered

If the Driver turns off GPS, Trip Master stops receiving live location updates. The last known location remains visible. The Shipper and Dispatcher will see that GPS is inactive. The Driver's session remains open — GPS simply resumes when the device enables it again. GPS status is logged, meaning any significant gaps are visible to Admin in the audit trail.

Disputes must be submitted to BtSh Admin within 7 calendar days of the event:

• Email: support@btsh.africa
• Admin: admin@btsh.africa

Include your load reference, the nature of the dispute, and any evidence. Disputes submitted outside the 7-day window may not be eligible for investigation.

Yes. Admin can intervene where delays, emergencies, poor coordination, or fraud risk may affect a load. Admin actions include force assignment to another Carrier, escrow hold, account restriction, and reporting to relevant Nigerian law enforcement where applicable. All Admin interventions are logged with timestamp and reason.

Carrier payouts are designed to process within the same business day of GPS milestone confirmation, subject to Admin approval and bank processing. For Dispatchers, commission is credited to wallet after each completed load and withdrawable on request.

Yes. BtSh may freeze wallet funds where there is reasonable suspicion of fraud, chargeback activity, identity issues, or breach of the Terms of Service — pending investigation. Users are notified where reasonably practicable. Any frozen funds that are determined to be legitimate are released in full after investigation.