Answers for every
step of driving.

Start from the AkiGO Driver page or driver experience, create an account, provide accurate identity and contact information, and complete the required onboarding steps for your selected market.

Driver onboarding may require identity details, contact information, driver-license information, vehicle details, insurance, registration, profile verification, and market-specific records.

AkiGO may collect driver interest before onboarding opens. Registering interest does not guarantee approval, activation, or a launch date.

No. Information and documents must be accurate, current, readable, and associated with the applicant or eligible vehicle as required.

Visit the Driver Requirements page for general eligibility, vehicle, document, screening, and market-dependent information.

AkiGO reviews the submitted account, identity, license, vehicle, insurance, and other required information. Additional screening or clarification may be requested.

Review time can vary based on document completeness, screening providers, market requirements, applicant volume, and whether additional information is needed.

No. Meeting general requirements does not guarantee approval. Final eligibility depends on completed review, applicable standards, market access, and account status.

An application may remain pending because a document is missing, expired, unreadable, under review, inconsistent with other information, or because market onboarding is not yet active.

Yes. AkiGO may review eligibility again when documents expire, account information changes, safety concerns arise, or market requirements are updated.

A driver can go online only after the account is approved, required documents are current, the selected market is active, and the driver is eligible for the available service type.

Possible reasons include pending approval, expired documents, an account restriction, an active trip, unsupported market access, connectivity issues, or a temporary system problem.

The driver experience is designed to let eligible drivers control when they go online, subject to market access, account status, and operational restrictions.

Market access may depend on local requirements, approved documents, vehicle eligibility, insurance, permits, and account configuration. Approval in one market does not automatically authorize another.

The driver experience may show a connection warning, pause updates, or prevent online activity until reliable network and location access are restored.

When an eligible trip is assigned or offered, the driver experience is designed to show the available pickup, destination, route, driver-pay, timing, and request details before acceptance.

No. Offers may depend on admin dispatch, distance, service eligibility, vehicle type, rider requirements, driver status, market rules, and other operational criteria.

Eligible offers can generally be accepted or declined within the time shown. Repeated behavior may still be subject to applicable driver standards and account policy.

An expired offer is no longer available to accept. It may be reassigned, cancelled, or returned to dispatch depending on the trip workflow.

No. The platform should protect against duplicate acceptance and confirm only one eligible assignment.

A trip may disappear because it expired, was reassigned, was cancelled, no longer matched eligibility, or the account lost online or connection status.

The driver experience is designed to show driver pay, completed-trip activity, incentives, adjustments, and payout progress without displaying rider fare, platform margin, or internal commission information.

AkiGO is designed to present driver-pay information with eligible trip offers before acceptance.

Driver pay is generally recorded after the trip or delivery reaches an eligible completed state and required payment or review steps are satisfied.

Adjustments may result from approved waiting time, cancellation handling, incentives, route changes, corrections, disputes, or other trip-specific review.

Completed-trip and earnings activity should appear in the driver earnings, trip history, or wallet sections when available.

Supported methods may include an eligible bank account and an eligible debit card for faster payout where available.

Timing depends on the payout method, account verification, banking network, processing schedule, weekends, holidays, reviews, and provider availability.

A payout may remain pending because it is processing, under review, waiting for bank settlement, affected by a weekend or holiday, or blocked by an account or payment-method issue.

A payout can fail because of invalid bank or debit-card information, an unsupported account, provider rejection, verification issues, balance restrictions, or a temporary processing problem.

Instant or faster payout may be available only for eligible drivers, supported debit cards, qualifying balances, and active markets. Fees or limits may apply where disclosed.

Check the payout status, payment method, account details, processing date, and bank activity. Contact driver support with the payout reference if additional review is needed.

Call local emergency services immediately when there is immediate danger. Use AkiGO safety or support tools afterward when it is safe to do so.

Use the in-app safety or support workflow and include accurate trip details, messages, photos, and any other relevant information.

Drivers should prioritize immediate safety and follow applicable law and AkiGO safety guidance. Use the appropriate trip, cancellation, or support workflow and move to a safe location when possible.

Available tools may include trip sharing, emergency workflows, rider communication, incident reporting, unsafe-pickup reporting, trusted contacts, and support access.

Use the approved lost-item or support workflow. Do not share unnecessary personal contact information or arrange unsafe handoffs.

Use the Help Center, Contact page, or in-app driver support workflow when available. Choose the category that best matches the account, trip, document, earnings, payout, or safety issue.

Include the driver account email, relevant trip or payout reference, date, approximate time, screenshots where appropriate, and a clear description of the problem. Do not send passwords or complete payment-card numbers.

Use the driver document or account workflow to upload the current replacement. The account may remain restricted until the document is reviewed and accepted.

Use the account-support workflow and provide the email or phone number associated with the driver account. Do not create duplicate accounts to work around an access problem.

AkiGO should not claim continuous support coverage unless that service is operational. Available channels and response expectations will be shown in the applicable experience.