Difference between revisions of "Template:PDC"
From Cloud9 Payment Processing Gateway Documentation
(Created page with "Optional Payment Device Controller (PDC) hides the complexity of low level communications with the payment terminals and adds the Store and Forward functionality, if desired....") |
|||
| Line 2: | Line 2: | ||
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. | ||
| + | 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. | ||
| + | |||
<br> | <br> | ||
Revision as of 19:41, 31 October 2016
Optional Payment Device Controller (PDC) hides the complexity of low level communications with the payment terminals and adds the Store and 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. |
