Documentation # Data Model
GoDaddy Poynt API resources allow developers to process merchant information in a multitude of ways following the established data model.
This model is integrated by key components that are essential for the correct performance of merchant operations. They also ensure a comprehensive approach when developing different types of solutions.
# Payments
Within payments, you will find elements that represent the request to purchase a product, the financial exchange, and the parties involved. It also includes additional operating elements for domain association, merchant details, among others.
At the same time, every element in that interaction will have a number of possible actions in relation to the purchase. It's essential to understand every action in order to use them correctly.
Below are the data model graphics for two of the most important elements; orders and transactions.
# Merchants
Merchants are the small businesses for which the Poynt system assumes a business hierarchy. There will be a parent business at the root, and each business could have 0 or more stores.
In cases where businesses have multiple stores, each store can have 0 or more terminals. This resource provides operations to create, update and view the entire hierarchy in different cases. Below are the main elements integrating the Merchant section.
# Products
Products corresponds to the item or service provided by the merchant to the final customer. Based on the wide variety of industries working with smart terminals, merchants can have multiple products. For this reason, the products section allows developers to interact with several elements as shown below
# Notifications
The notifications component includes three main elements.
Cloud Messages (opens new window) - You can use it to send Messages to the cloud applications running on the Smart Terminal.
Hooks (opens new window) - It allows you to register their application to receive callback events from Poynt or replay missed events.
Delivery (opens new window) - When a event matches the registered Hooks of an application, a delivery is made to the registered delivery URL.