Overview
The type of point of sale (POS) used for a transaction must be specified so that the PayConex™ Gateway and Payment Processor can accurately identify the origin of the transaction. This information is key for the following factors:
- Security: Ensuring appropriate security measures are applied.
- Compliance: Meeting regulatory and legal requirements.
- Routing: Efficiently directing the transaction through the network.
- Fraud Prevention: Detecting and mitigating suspicious activities.
- Support: Facilitating efficient technical support and troubleshooting.
Specifying the POS type ensures secure, compliant and efficient transaction processing.
Note
Note that the POS profiles and entry modes are assigned by default for PAX transactions via BluePOS given the fact that these are Bluefin P2PE certified devices. For more information, see:
For an in-depth overview of profiles for device transactions, review Device Profiles.
Point Of Sale Profiles Table
Some of the POS profiles have the same sub-type but serve different purposes. For example, both ECOMMERCE and SERVER have the "ECOMMERCE" posType.
Here is a table of possible POS types based on GET /api/v4/pos-profiles:
| Name | POS Type | Description |
|---|---|---|
ATTENDED_ON_PREM_POS | ON_PREMISES_ATTENDED_POS | On Premises Attended POS. |
UNATTENDED_ON_PREM_POS | ON_PREMISES_UNATTENDED_POS | On Premises Unattended POS. |
ATTENDED_OFF_PREM_POS | OFF_PREMISES_ATTENDED_POS | Off Premises Attended POS. |
MOTO | MOTO | Call center using a digital capture. mechanism, such as a Hosted Payment Form |
P2PE_MOTO | MOTO | Call center or back-office application using a terminal to key in data. See CIT/MIT Use Case and Mail/Telephone Order Transactions. |
ECOMMERCE | ECOMMERCE | Transaction initiated from a website. |
SERVER | ECOMMERCE | Transaction initiated from a server, such as a refund or reissue (Merchant Initiated Transaction). |
ACH | ECOMMERCE | ACH Transactions. |
Entry Modes
Our PayConex™ Gateway supports different entry modes through the V4 API, depending on the posProfile.
These can be used as optional in combination with the posProfiles but are usually automatically assigned.
| Entry Mode Name | Description |
|---|---|
CONTACT | The transaction is initiated by inserting the chip card into a card reader, requiring physical contact between the card and the terminal. |
CONTACTLESS | The transaction is conducted by tapping or waving the card near a contactless-enabled terminal, using RFID or NFC technology for communication. |
NFC | Near Field Communication technology is used to conduct the transaction, typically involving mobile devices or contactless cards. |
SWIPE | The transaction is completed by swiping the magnetic stripe of the card through a card reader. |
KEYED | The transaction data, such as card number and expiration date, are manually entered into the terminal, usually when the card cannot be physically read. This includes the posType of MOTO and ECOMMERCE. |
FALLBACK_SWIPE_TERMINAL_FAIL | The transaction falls back to swiping the card's magnetic stripe because the terminal failed to read the chip. |
FALLBACK_SWIPE_EMPTY_LIST | The transaction falls back to swiping the card's magnetic stripe because the terminal could not access the necessary data from the chip. |
Also see
To see these two combined in use manually, consider the following examples: