DoorDash login: choose the customer, Dasher, or merchant route

01 · three account contexts

Choose the surface that matches what you need to do

A customer orders food and goods through DoorDash. A Dasher accepts and completes deliveries. A merchant manages a store, menu, orders, staff access, and payments. DoorDash publishes separate help areas for these audiences, and the controls exposed after login reflect those different responsibilities.

1. 01

   Name the account role before opening a login.

2. 02

   Use a saved official app or DoorDash-owned starting page.

3. 03

   Check both the hostname and the role displayed.

4. 04

   Move to the matching official support center if access fails.

02 · customer route

Customer sign-in begins with the ordering service

For an ordering account, open https://www.doordash.com yourself or use the official DoorDash mobile app. The site exposes its own Sign In control. Do not search for a separate “account verification” page when an order, refund, DashPass renewal, or delivery problem creates urgency. Begin again from the service you already use.

DoorDash’s customer help center has a Manage Your Account category for account details and protection questions. Use that official support surface for recovery or account changes. A driver or merchant article may discuss a related credential, but it is not the best authority for a customer workflow.

03 · Dasher route

Dasher access is centered on the Dasher app and support flow

DoorDash’s Dasher materials direct active Dashers to the Dasher app for work and support. The public Dasher site also supports signup and signup-status flows. DoorDash’s signup documentation says an existing consumer and Dasher account can be connected and describes a doordash.com Dasher login route, including a verification step during signup.

That relationship does not justify entering a customer password into any page labeled “Dasher.” Confirm that the host remains under doordash.com and that the flow began from the app, Dasher Central, or official support. A request for a live code from someone claiming to be support is not part of verifying your own browser session.

04 · merchant route

Merchant Portal access carries payment and store risk

DoorDash’s merchant documentation tells merchants to navigate to the Merchant Portal and sign in with the account email and password. The portal can expose store operations, performance, menus, and payments. That makes merchant credentials and staff invitations especially valuable to attackers.

Enter through https://merchants.doordash.com and use its Login control, or use an existing bookmark created from that official route. Treat banking-change messages, ownership transfers, refund claims, and “store paused” warnings as unverified until checked inside the portal. Never approve a factor prompt or share a code to help a caller “secure” the store.

05 · fake-page checks

Read the host, not the role word

A hostname such as merchant.doordash.com.verify-store.example is controlled under example, not doordash.com. Likewise, an address on refund-check.example is controlled by that domain even if the name before it mentions DoorDash. A padlock does not change who controls the hostname.

DoorDash may use different official subdomains and identity pages during a real flow. Evaluate the whole transition: where you started, the registrable domain, whether the role matches, and whether the prompt is expected. When evidence is incomplete, close the page and return through the official app or site.

06 · recovery and containment

Use role-specific support and protect any working session

If one device remains signed in, keep it available while investigating. Use the customer, Dasher, or merchant support center that matches the account. Do not repeatedly reset a password from several routes; DoorDash’s own Dasher guidance notes that customer and Dasher credentials can be related, so a change may affect more than one experience.

After suspected compromise, review account details, orders, addresses, payout or banking information, staff access, and active devices where the applicable product exposes them. Contact the payment provider or bank through a known channel if financial details changed. This guide does not claim a universal DoorDash session-removal or factor-setting path because the official workflows differ by role and can change.

Continue safely

Related sign-in guides

• Five9 login and identity-provider routesA separate route and evidence boundary.
• Find your employer’s Workday sign-inA separate route and evidence boundary.
• What passwordless login meansA separate route and evidence boundary.