We’ve published our Developer Documentation to help you get started with integrating Paylias as a payment network. Whether you’re an issuer, acquirer, or building an application that interacts with aliases and payments, the documentation aims to provide the reference points and workflows you’ll need to implement each part of the system.
The docs are still evolving, and we expect to make continuous improvements as more developers build on top of Paylias. If you spot anything that’s missing, unclear, or incorrect, we’d really appreciate your feedback.
The documentation is organized into four main sections: Concepts, Tutorials, and an API Reference.
The Concepts provide conceptual overviews and common implementation flows. These are useful if you’re trying to understand how something fits together or how a specific part of the system is expected to behave.
Some examples include:
Each guide is meant to complement the API reference by showing how different endpoints are used in context.
The Tutorials are step-by-step walkthroughs intended to help you build out specific parts of your integration. One tutorial we’d recommend starting with is the Incoming Payments for Issuers guide. It walks through how to handle incoming webhook events, persist payment requests, run internal checks, and send a response back to Paylias.
In this guide, we walk you through how to create a Next JS application that integrates with Paylias to handle incoming payment requests. It covers all the important pieces like handling webhooks, responding to payment admission tasks and showing your users a UI to approve or reject a payment they initiated.
If you’re integrating Paylias as an issuer, this tutorial should be helpful in understanding the webhook-driven flow of incoming payments.
The API Reference includes the full specification of each resource and endpoint. All endpoints are documented with request and response schemas, supported parameters, and example responses.
We’ve also included a sandbox environment, so you can try out requests directly in the documentation without needing to set up external tooling. This should help when testing request formats or debugging your integration.
We’ve tried to make the documentation easy to navigate and focused on the most relevant tasks developers need to perform. That said, documentation is never finished and your feedback will help us prioritize improvements and fill in any gaps.
If anything is unclear, broken, or missing, please feel free to reach out. You can leave feedback directly in the docs UI or email us at ziyad@paylias.xyz. We’d be very grateful.
You can view the full documentation at apidocs.paylias.xyz. We suggest starting with the guides to get a sense of how the system works, then working through the issuer tutorial if you’re building support for incoming payments. From there, you can explore the API reference and test requests on our sandbox environment.
Thanks for taking the time to explore Paylias. We’re looking forward to seeing what you build!