PayLink APIs are organized around Representational State Transfer (REST) architecture and are designed to have predictable, resource-oriented URLs and use HTTP response codes to indicate API errors. Below are the API endpoints:

1. Live Server: https://www.payfabric.com
2. Sandbox Server: https://sandbox.payfabric.com

Want to get started with PayLink API integration? Here's a quick check list:

1. Configure a PayLink service, check out the Configure Portal to learn how.
2. Read up on how to authenticate with our APIs.
3. Read up on how to handle errors with our APIs.
4. Browse the API docs for the API you need to work with.
5. Have a question or need help? Contact [email protected].

PayLink clients require PayFabric Device ID and Device Password to authenticate with APIs.

We have a detailed guide in our PayFabric documentation for more details.

PayLink uses HTTP response codes to indicate the status of requests.

We have a guide detailing the meanings of the most common response codes that you will encounter.

PayLink sends and receives payloads as structured JSON Objects. Many of these objects are used in both requests and responses. Some of the objects (like Address or Cardholder) are embedded as child elements of other objects.

• Create a PayLink
• Update a PayLink
• Retrieve a PayLink
• Retrieve PayLinks
• Retrieve a PayLink URL
• Remove a PayLink
• Cancel a PayLink
• Get Post Data
• Update Post Data
• Resubmit Post Data

• Create a Wallet Link
• Retrieve a Wallet Link URL
• Cancel a Wallet Link

• Resend PayLink Notification Email
• Resend PayLink Notification SMS
• Retrieve Notification Templates

• Create Template
• Update Template
• Copy Template
• Delete Template
• Set Default template
• Get Templates

Please tell us how we can make the APIs better. If you have a specific feature request or if you found a bug, please contact [email protected]. Also, feel free to branch these docs and send a pull request with improvements!