Reasons to Swap Out Your Current Credit Card Solution and replace it with PaymentCardXpress® (PCX) - #5 Supports NoCode Options
What is “NoCode”?
CFXWorks has implemented several key features into PaymentCardXpress (PCX), which we call our NoCode Option, intended to reduce the skills, resources, and lines of code required by the merchant to help them implement an integrated solution. We believe that our NoCode Option will:
- Help our customers select the integration technology that best fits their needs.
- Reduce the skills, resources, and time required to complete an integration effort.
- Assist in managing the integration process.
There are five major components to the PCX NoCode Option:
- Web Interface Options – changes that can be made to the web services user interface that allow the merchant to change the look-and-feel of the menus displayed by PCX. Colors, text, and menu options can be changed by editing a configuration file and a style sheet rather than writing code.
- Integration Options – PCX supports several different integration technologies allowing the merchant to optimize how they integrate their front and back office systems by matching their integration choices to best fit their skills and resources. These options include:
- Files – Using files to pass transaction requests and responses between code written by the merchant and PCX.
- Database Queues (DBQ) – Using database tables to queue transaction requests and responses passing between code written by the merchant and PCX.
- iSeries Data Queues (iSeries only) – Using data queues to pass transaction requests and responses between code written by the merchant and PCX.
- Sockets – Using TCP/IP sockets to pass transaction requests and responses between code written by the merchant and PCX.
- Browser – using HTML, JSP, and XML to pass transaction requests and responses between code written by the merchant and PCX.
The following figure illustrates our approach to providing our users multiple integration options. For example, assume you are a merchant running your business using an IBM iSeries platform. Your order entry program most likely is written in RPG, running on your iSeries host, using data queues, displaying the order entry menus using a 5250 emulator.
The track displayed in red (1-4) illustrates how one might choose to integration an order entry application with PCX. The track displayed in black (5-9) is what PCX is responsible for. PCX logs the detailed transaction data, request and response, to an audit database. Under the covers, PCX uses Elavon’s Fusebox technology to capture all sensitive card data. PCX has NO VISIBILITY to the sensitive card data. The Primary Account Number (PAN) is replaced by a token in the audit database. Most organizations integrate their back-office systems by simply querying the audit database for detailed transaction information. The track displayed in green (1-4) shows how one might choose to integrate a shopping cart solution with PCX. Note that the activities performed by PCX related to your back-office systems, remains the same.
Figure 1 – Integration Options
Receipts Options – The card associations have their fingers in everything including precisely what must be displayed in the receipt you provide to your customer. The merchant can make changes to the information they are permitted to change on the receipt, using the NoCode feature. Changes are made by editing a configuration file rather than by editing or adding code.
Card Association Rules – We have attempted to identify the processing rules implemented by the card associations and processors and enforce the including rules that if ignored, would increase your processing fees.
PCI-DSS Requirements – We strictly enforce the fact that PCX HAS NO VISIBILITY TO THE PRIMARY ACCOUNT NUMBER. Therefore, PCX is “Out-Of-Scope” for PCI-DSS. This reduces the merchant’s Self-Assessment Questionnaire (SAQ) scope of responsibilities to SAQ A or SAQ-P2PE.
Credit Card Analytics – Analytics is being applied in many ways within the IT industry. Our focus is on the discovery, interpretation, and communication of meaningful patterns in transaction and data usage and applying those patterns towards effective decision making and process automation intended to improve customer service, reduce merchant costs, and reduce the time and resources required to manage the payment process.
What does it mean to me?
CFXWorks believes that it means:
- “look-and-feel” flexibility!
- The ability to change “look-and-feel” without writing code!
- More options!
- Less skill intensity!
- Reduced time-to-market!
- Lots of options!
- Lower cost!