Stripe onboarding was cancelled

Return to the Stripe card

If the Stripe onboarding window was closed, cancelled, or returned to Reslify before setup was ready, open Settings / Integrations and return to the Stripe card. The panel shows the current account state and the next safe action from that card.

Use the action that matches the card:

1. Not connected means no Stripe connected account is stored for the restaurant. Select Connect Stripe.
2. Action required means a Stripe account exists, but Stripe still needs details or has pending requirements. Select Complete setup.
3. Under review means details were submitted, but Stripe has not enabled charges yet. Wait for Stripe verification, then select Refresh status.
4. Ready means details are submitted, there are no pending requirements, and charges are enabled.

Start from a fresh Stripe link

Do not use an old Stripe hosted onboarding link from browser history, chat, email, or a previous tab. Stripe account links can expire, and the old link may send you back to Reslify without completing setup. Always create a current link from Connect Stripe or Complete setup on the Reslify Stripe card.

Complete the hosted Stripe flow in the same session. Stripe may ask for business details, representative information, bank or payout details, identity verification, terms of service, tax details, or additional information. When Stripe returns you to Reslify, select Refresh status so the panel reads the latest connected account state.

When Stripe reports missing requirements, Reslify groups them on the card as Personal details, Business details, Bank account, Identity verification, Terms of Service, or Additional information required. Select Complete setup again and resolve the listed group in Stripe.

Fix redirect or browser issues

The onboarding handoff redirects the current panel tab to Stripe and then back to Settings / Integrations. If the handoff does not open, returns immediately, or shows the cancelled message again, try these checks:

1. Refresh Settings / Integrations, then select Connect Stripe or Complete setup again.
2. Allow redirects and Stripe popups for the panel browser session, especially if Stripe asks for identity or bank verification.
3. Disable browser extensions that block third-party payment, identity, or tracking flows, then retry from the Stripe card.
4. Use a normal browser window instead of an old private window if the Stripe session has lost cookies.
5. Sign out of the panel, sign back in, and restart from the Stripe card if the card action repeatedly fails to start.

If the browser lands on a Stripe refresh page, let Stripe continue to the refreshed link. If that still fails, return to Reslify and start again from Complete setup so the API creates a new hosted onboarding link for the same connected account.

Check the state before launch

Cancelled onboarding does not by itself break basic reservations, but Stripe-backed payment flows must wait for Ready. Do not publish Stripe-dependent deposits, Prepay, the pay-now side of Optional Prepay, Card required guarantees, or Stripe gift-card checkout while the Stripe card is Not connected, Action required, or Under review.

When to contact support

Contact support from the panel if:

1. Stripe says onboarding is complete, but Reslify still shows Action required after Refresh status.
2. The card stays Under review longer than Stripe's verification guidance or the restaurant has already resolved the requested Stripe checks.
3. Connect Stripe, Complete setup, or Refresh status shows a failure toast after retrying from a fresh panel session.
4. The browser repeatedly returns with Stripe onboarding was not completed. You can resume setup anytime. even after allowing redirects and starting from the Stripe card.

Include the restaurant name, the current Stripe badge, the action you selected, any requirement groups shown on the card, the Stripe account email used, the time onboarding was completed or cancelled, and any browser error or toast text.