> For the complete documentation index, see [llms.txt](https://pingbusiness.gitbook.io/pingbusiness/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pingbusiness.gitbook.io/pingbusiness/integration/create-your-store-guide/part-2-deploying-your-store.md). # Part 2 - Deploying Your Store Before following Part 2, you would have completed customizing and able to preview your store following the steps in [Part 1 - Customize Your Store](/pingbusiness/integration/create-your-store-guide/part-1-customize-your-store.md). In Part 2 of this guide, you will deploy your store online using cloud platform like Railway - akin to you putting your shop on a rented space for your customers to access. This is where you’ll add a payment card, and where you will need to manually complete the 3 out of the 4 manual steps highlighted [here](https://app.gitbook.com/o/oYomLlwEvVT7beZsoP4V/sites/site_UtrOv/s/Eh8xmgV7S0jCh1wRA50D/~/edit/~/changes/11/integration/create-your-store-guide#what-you-will-need-to-do-besides-pasting-the-prompt) {% hint style="info" %} This part rarely runs start to finish without pausing. It will reach things it can’t decide alone and it will ask. That’s normal, not a fault - you’ll get several questions across Part 2, and answering them is the process. {% endhint %} {% stepper %} {% step %} ### Fill in where the store should live 1. Go back to the store launcher and click Tab 2. Deploy store. 2. Environment - choose Staging / test for your first run. This is practice mode. 3. Hosting platform - choose Railway. 4. Store DNS hostname - the address you want. If you don’t own one yet, put anything sensible; you’ll be offered a free Railway address later. 5. Merchant and Store identifier - already filled in, because you came from your store page. Just check they look right.

(1) The Deploy store tab (2) practice or real (3) Railway (4) Pre-filled for you {% endstep %} {% step %} ### Hand over the deployment instructions 1. Click Copy prompt and paste the prompt into Cursor - using the same conversation as Part 1 is the ideal option, as the workflow still has your shop design. 2. Send the prompt.

(1) Your key is deliberately left out (2) Copy and paste the prompt into Cursor {% hint style="warning" %} **Note the warning:** your merchant key is deliberately not in them. {% endhint %} {% endstep %} {% step %} ### Answer the workflow questions Before creating anything, Cursor will ask you a handful of questions - read the options \ and pick one.

(1) The prompt (2) The options, including doing it yourself

Cursor and any other AI assistant will not ask or accept merchant key in the chat. Every option keeps it out of the conversation. The answers most people want: • **Railway access** - let it use the command-line tool after you log in yourself. You stay in control of the login. • **Where the code lives** - let it create a private repository and push your shop there. Railway builds from that. • **Your merchant key** - the option where you type it into Railway’s own field, or into a file on your machine. Never the chat. {% endstep %} {% step %} ### Approve the workflow Cursor will show you each command before running it and waits for your approval - you can run once, or let it run this kind of command from now on.

{% hint style="info" %} You’re being asked to approve the commands, not to review. If you’d rather not think about it each time, choosing the “always allow this kind of command” option is reasonable \- you can still stop it at any point. {% endhint %} {% endstep %} {% step %} ### Do the manual tasks During this run, you will need to do 2 tasks manually as highlighted [earlier](https://app.gitbook.com/o/oYomLlwEvVT7beZsoP4V/sites/site_UtrOv/s/Eh8xmgV7S0jCh1wRA50D/~/edit/~/changes/11/integration/create-your-store-guide#what-you-will-need-to-do-besides-pasting-the-prompt). 1. Sign into Railway 2. Make sure you have a paid plan on Railway

Notice it flags the plan before creating anything: six services plus a database won’t run on a free trial. That’s the right order - you get to decide before any money is involved. {% hint style="info" %} **This is the one moment your secret key is involved.** It goes into a file on your own computer - never into the chat. From there it goes straight into Railway’s protected settings. If your assistant ever asks you to type your key into a chat message, refuse, and tell it to use the file instead. {% endhint %} {% endstep %} {% step %} ### Sign in to Railway

You can run the command to login on behalf via command (1), or login via the link provided in (2). The command hands you a link and a code rather than trying to drive your browser. The account you sign in with is the account that gets billed.

1. If you’d rather not run commands yourself, just ask it to run the login for you. 2. Open the link provided, or go to the activate page and type the code. 3. Sign in - or create a Railway account there if you don’t have one. 4. Come back and tell it you’re done. {% endstep %} {% step %} ### Check your plan on Railway

(1) Your current plan (2) Your projects **IMPORTANT:** Adding a card is not the same as being on a plan that can run a shop. If you stay on a trial or free tier, the next attempt fails with a message about limits or resources. Move onto Hobby plan ($5 a month) or higher at the same time as adding the card, and you’ll skip a whole round of confusion. {% endstep %} {% step %} ### Let it build and check the work {% hint style="info" %} This part may take approximately 30 - 60 minutes for the process to complete. {% endhint %} Back to Cursor, you should have Railway access enabled with the prompt working now to build the store without requiring further action during this step.

(1) Making sure the blocker is cleared (2) What will be built first

Cursor will run the kit’s acceptance checklist and scans the live page for leaked secrets before telling you it is done. At this step, you don't have to watch every action. Go and do something else, and if it hits a problem, it will stop and tell you - you can refer to [Store Launcher Troubleshoot Guide](/pingbusiness/integration/create-your-store-guide/troubleshooting.md) to navigate issues that happen here. {% endstep %} {% step %} ### Congratulations! Your store is now live

Your store's web address will be shared with you, and shows the checks it passed. Only the front door is public - everything else is private, with the live page tested for you. Here's what you need to do next: 1. Access the web address. The website should load, with your specified store name and brand colours. 2. The address starts with https\:// and your browser shows a padlock. 3. Create a test account and sign in. 4. Add something to the basket. 5. In practice mode, place a test order and confirm it appears in your PingBusiness dashboard. {% hint style="info" %} If you used the free web address, it’ll be a long automatic one like edge-production-0d29.up.railway.app. That’s normal, and the padlock is real. When you’re ready, give it a domain you own and ask it to switch the shop over. {% endhint %} \ **That's it! Your shop is online.** When you’re ready for real customers, ask it to run the same process again with **Production** instead of **Staging / Test**, using your live merchant key, and turn off **Test Mode** in your PingBusiness dashboard. {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://pingbusiness.gitbook.io/pingbusiness/integration/create-your-store-guide/part-2-deploying-your-store.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.