Skip to content
Question about project billing transfer options
evanckennedy
OP

2 months ago

I'm currently hosting a small project for a client on my personal Railway account under the Hobby plan using my own credit card. My client wants to take over paying for the server costs directly so they don't have to keep reimbursing me.

Could you please let me know what options are available to transfer the billing or have a client's payment method cover a project currently hosted on my personal account?

Thanks.

Solved

5 Replies

Railway
BOT

2 months ago

You can transfer your projects to the account you would like by following our documentation here: https://docs.railway.com/guides/projects#transferring-projects

Please note that the instructions vary based on the subscription type you are transferring from and to.


Status changed to Awaiting User Response Railway • about 2 months ago


Railway

You can transfer your projects to the account you would like by following our documentation here: <https://docs.railway.com/guides/projects#transferring-projects> Please note that the instructions vary based on the subscription type you are transferring from and to.

evanckennedy
OP

2 months ago

can i have a non-bot answer?


Status changed to Awaiting Railway Response Railway • about 2 months ago


2 months ago

Billing is tied to the workspace, not to individual projects. That means the client can't put their card on a single project inside your personal workspace. The way to do this is to move the project into a workspace the client pays for.

First, the client creates their own Railway account and starts a Hobby or Pro plan with their card. Next, you invite them as a member from the project's settings, in the Members section. Then you click the three dots next to their name and choose Transfer Ownership. Both workspaces need an active Hobby or Pro plan for the transfer to work. Your account also needs two-factor verification turned on to start it.

The client gets an email and has 24 hours to accept. Once they do, the project and its usage bill to their workspace, and your card stops paying for it. You can stay on the project as a member if you still need to work on it. The full steps are in our project transfer docs.


Status changed to Awaiting User Response brody • about 2 months ago


brody

Billing is tied to the workspace, not to individual projects. That means the client can't put their card on a single project inside your personal workspace. The way to do this is to move the project into a workspace the client pays for. First, the client creates their own Railway account and starts a Hobby or Pro plan with their card. Next, you invite them as a member from the project's settings, in the Members section. Then you click the three dots next to their name and choose Transfer Ownership. Both workspaces need an active Hobby or Pro plan for the transfer to work. Your account also needs two-factor verification turned on to start it. The client gets an email and has 24 hours to accept. Once they do, the project and its usage bill to their workspace, and your card stops paying for it. You can stay on the project as a member if you still need to work on it. The full steps are in our [project transfer docs](https://docs.railway.com/projects#transferring-projects).

evanckennedy
OP

2 months ago

Thanks for the breakdown. Just a couple of quick questions before I do this:

Will the app URL and API endpoints stay exactly the same? Also, will I still be able to push updates from GitHub and access logs/troubleshoot normally, or does he need to grant my account specific permissions after the transfer?


Status changed to Awaiting Railway Response Railway • about 2 months ago


2 months ago

Yes, the URL stays the same. The transfer moves the project with its services intact, so the Railway-generated domain your app uses today and the GitHub repo connection on the service carry over unchanged, and your API endpoints keep working at the same address.

On access, one correction to the earlier steps: when the transfer completes, the project's member list is cleared, and that includes you. Your client will need to invite you back from the project's settings, in the Members section. Once you're a member with the Member role, you can view logs, change variables and service settings, and deploy, which covers normal troubleshooting (workspace roles).

GitHub pushes will keep auto-deploying as long as at least one project member has a connected GitHub account with contributor access to the repository (autodeploy requirements). Since the repo is yours, being added back to the project covers that.


Status changed to Awaiting User Response brody • about 2 months ago


Status changed to Solved evanckennedy • about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...