Objects
We love objects. On this page we give an overview of all objects within our platform.
Object code | Object | Description |
---|---|---|
A | Account | Every person that works in the GMS gets an personal account, that can be connected to one or more merchants. Account can login via an email address, password and a 2FA-authenticator. |
AG | Authorisation group | A group of rights that can be assigned to a Merchant (to perform some actions or view certain data), accounts (via the license) or to a Token (for API / platform access). |
AL | License | The entity that is connecting the account and a merchant, based on authorisation groups the user gets access to (a part) of the merchant data. |
AS | Address | Physical address that can be assigned to a service, terminal, merchant, payer or account. |
AT | API token | API tokens are used to be able to link software with the platform of Pay. API tokens consist of a Token code starting with AT combined with a token hash of 40 characters. Authorisation groups can be assigned to an API token to enable certain functionalities. |
BA | Clearing account | A merchant's revenue is cleared via its IBAN number. Merchants can have multiple clearing accounts assigned to different service locations, which makes it possible to split clearings and invoices. |
CA | Company address | A location where a merchant deploys their activities. Must be the physical address of the management as it is assigned to the company main address. Postal addresses as allowed as addition to the main address. Per Sales Location you can assign the 'main location' for eCommerce or add one extra Store or Outlet location for In-person payments. |
CD | Chargeback dispute | When a merchant receives a creditcard chargeback, they will always be notified by email. If the merchant decides to dispute this chargeback then a chargeback case will be created. |
CM | Contact method | Information assigned to a merchant, which can be public contact information or used for notifications only. We use contact methods for merchants, partners and integrators. If the data is public, we can share it in payer communication. |
CP | Packages | The servicegroup we, or the partner uses, to set up a proposition, based on the target group. A package can have pricing, clearing cycles, holdback and payment settings. When a merchant is initially registered we connect them to a Package. |
CT | TurnoverGroup | A Group that can be used to assign serviceLocations. A TurnoverGroup can has his own clearingAccount. Fee's and Clearing can be split by using TurnoverGroups. |
CY | Category | Pay. uses categories such as baby and kids, bike stores etc. to display what is being sold at a service location. The category is also linked to a risk factor, the mimimum required package and the available payment options. |
D | Document | Pay. requires various documents to complete the boarding proces, such as a CoC extract, UBO form, etc. In addition there are also documents that are not related to the boarding process, the so-called addendum, which are often added later. |
EX | External transaction | Each payment attempt by a customer has a unique reference in Pay. The external transaction objects holds all different kind of data like user ip address, payment option, transaction amount and optional order and productdata. |
I | Invoice | Every week or month an invoice is generated for the merchant stating the transaction costs, package costs and/or terminal costs. At default invoices will be paid via an internal payment, but it can also be paid through a direct debit or a manual banktransfer. |
LA | Login attempt | Each attempt to login into our portal will be registered as an login attempt. |
LY | Look & feel template | A merchant or partner can create a look&feel template to customize their checkout, those can be assigned to the partner, merchant or service. |
M | Organisation / Merchant | Mostly used for Merchants (companies who use our platform to proces payments, but can also be used for partners, vendors or other relations. An organisation needs to be onboarded, even when no payments are processed. If you work with us, you need go trough the boarding flow. |
MC | Merchant connection | The relation between Merchants or Organisations. If there is another merchant interacting with your merchant as ISO, Partner or Alliance, we create a relation between the organisations and assign an authorisation group to it. |
MV | SoftPos Payments | A Payments made via the SoftPos solution. |
PB | Issuer/payment bank | Financial institute that can be a Bank or Electronic Money Institute or a alternative payment provider like PayPal this is issuing a method to send or receive payments to there clients. |
P | Project | A shared cooperation between vendors, integrations, payment methods and companies, with a scope, budget and delivery moment. |
PL | Integration -plugin | A organisation can make a technical connection to our platform, can receive and certified integration. |
PV | Integration - version / Application | If an integration has more than one solution for different audiences or payment methods, or release a new version of their integration, we provide a new Id, that can be used to set up a service in pay. |
R | Roadmap Request | A new feature, payment method or object in the CORE-data to deliver that is on the roadmap. |
RT | Reporting ID | A transaction that has an endstate is put in our reporting engine. Based on the clearing cycles we can transfer the reported transactions to the merchants clearing account |
SL | Service (Location) | A Service contains the preferences of a merchant, including the URL, a description and a category. In addition you can also see which integrations is being used and which payment options are provided to the customers. |
SY | Sync task | Merchants can share their transaction data with external parties via a sync task. Pay. can send automated specification files to persons, departments and a couple of accounting systems. A sync taks can be scheduled daily, weekly, monthly or after a clearing and supports several CSV, MT940, XML formats. |
TH | Pin terminal | Pay. provides a number of different types of card terminals. The moment the terminal is linked to a merchant, a TH-code is allocated. This unique reference is important to determine which turnover must be allocated to a particular card terminal. |
TM | Trademark / tradename | Trade names are, where possible, placed on the statements and in communication with the payer. Depending on the package merchants can add trade names to a company, when checked can be used. |
W | Wish | A request to get something on our roadmap. A wish can be upvoted to get higher priority. We send notifications on status changes of upvoted wishes. |
XC | Chargeback | A transaction that is chargebacked can be disputed, so that a case is created in the platform. The case goes into remediation. |
Updated 3 months ago