Getting Started ​

The Payment Specification outlines a system that makes it simple for repository maintainers to accept payments in a secure fashion from numerous clients that choose to implement the specification.

At it's core, the system relies on a RESTful API hosted by the repository (known as a Payment Gateway). The client is responsible for making requests to this gateway to facilitate the protocol.

Client ​

Some examples of clients Package Managers such as Sileo or Zebra and online search tools such as Parcility or Canister. If you are implementing a Payment Specification Client, please follow the Client Documentation.

Server ​

Payment Gateways are typically hosted by the repository wishing to sell paid packages through the system. If you are implementing a Payment Specification Gateway, please follow the Payment Gateway Documentation.