PayFabric 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/v2/rest/api
2. Sandbox Server: https://sandbox.payfabric.com/v2/rest/api

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

1. Register and then configure a PayFabric account, check out the Quick Start Guide 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, you could also view our language specific examples.
5. Have a question or need help? Contact [email protected].

PayFabric clients have two ways to authenticate, Device ID and Password authentication and Security Token authentication.

We have a detailed guide for authenticating your users with our APIs.

PayFabric 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.

PayFabric 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 Transaction
• Update a Transaction
• Process a Transaction
• Create and Process a Transaction
• Retrieve a Transaction
• Retrieve Transactions
• Cancel (Void) a Transaction
• Capture a Pre-Authorized Transaction
• Credit a Transaction
• Refund a Customer

• Create a Credit Card / eCheck
• Update a Credit Card / eCheck
• Retrieve a Credit Card / eCheck
• Retrieve Credit Cards / eChecks
• Lock Credit Card / eCheck
• Unlock Credit Card / eCheck
• Remove Credit Card / eCheck

• Retrieve a Payment Gateway Profile
• Retrieve Payment Gateway Profiles

• Retrieve a Shipping Address
• Retrieve Shipping Addresses

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 documents and send a pull request with improvements!