PayString was previously known as PayID.
To familiarize yourself and experiment with PayString, you can set up a local PayString server. Here is a simple method. For more options, including PayString deployment for production environments, see Deployment Overview.
The reference implementation server is available at https://github.com/paystring/paystring. You can download the reference implementation server by cloning the repository at the command line:
git clone https://github.com/paystring/paystring.git
Go to the
/paystringdirectory that you just created:
Boot up the PayString HTTP server and a Postgres database to develop against:
npm run devEnvUp
Now that you have a PayString server running, you can create a PayString. If your server is publicly accessible, other people could query your account information from your PayString server.
To create a PayString, with an XRP Ledger Testnet account, send this request to your server:
PayString supports various payment networks. To create a second user with a Bitcoin testnet account, send this request to your server:
After setting up a server and creating a PayString on the server, the next step is to request the PayString from the server. The PayString Protocol is what allows you to make these requests. And, when the server is publicly available, other wallets and entities can make similar requests to query any PayString and related account information stored on the server.
To request the PayString you created for Alice:
The response should have the following payload:
To request the PayString you created for Bob:
That's it! You've set up a PayString server locally, created new PayStrings on your server, and requested those PayStrings by using the PayString Protocol.
If you want to clean up the Docker containers, you can run
npm run devDown.
Now that you've set up the basics, learn more about PayString and what you can do with it.