Difference between revisions of "Template:PDC"
From Cloud9 Payment Processing Gateway Documentation
| Line 1: | Line 1: | ||
| − | Optional [[Cloud9_Payment_Device_Controller_Setup|Payment Device Controller]] (PDC) hides the complexity of low level communications with the payment terminals and adds | + | Optional [[Cloud9_Payment_Device_Controller_Setup|Payment Device Controller]] (PDC) hides the complexity of low level communications with the payment terminals and adds [[Offline Store & Forward]] functionality, if desired. |
The client (POS/web page/mobile device, etc) can communicate with the PDC, which will in turn control the payment perminal/pin pad and relate the processing instructions to the Cloud9 Payment Gateway. | The client (POS/web page/mobile device, etc) can communicate with the PDC, which will in turn control the payment perminal/pin pad and relate the processing instructions to the Cloud9 Payment Gateway. | ||
This is the easiest form of integration and it is recommended. | This is the easiest form of integration and it is recommended. | ||
Revision as of 18:47, 22 August 2017
Optional Payment Device Controller (PDC) hides the complexity of low level communications with the payment terminals and adds Offline Store & Forward functionality, if desired.
The client (POS/web page/mobile device, etc) can communicate with the PDC, which will in turn control the payment perminal/pin pad and relate the processing instructions to the Cloud9 Payment Gateway.
This is the easiest form of integration and it is recommended.
Note: Variations of Payment Device Controller are Payment Mobile Controller (PMC) and Payment Web Controller (PWC), dealing with mobile and web based payment processing functionality respectively.
 |
| The client can communicate directly with the cloud or Payment Device Controller via SOAP, JSON or using the wizard like wrapper, written in C/C++/Java. |
