Integration

Payment Device Controller

The optional Payment Device Controller (PDC) hides the complexity of low-level communications with payment terminals and adds Offline Store & Forward functionality.

Optional component — The PDC is recommended for the simplest integration approach, but is not required. Clients (POS systems, web pages, mobile devices) communicate with the PDC, which controls payment terminals and relays instructions to the Cloud9 Payment Gateway.

Variations of the Payment Device Controller include:

  • Payment Device Controller (PDC) — local software for in-store terminal communication
  • Payment Mobile Controller (PMC) — mobile-based payment processing
  • Payment Web Controller (PWC) — web/cloud-based payment processing

Option 1: Local PDC with Store & Forward

Clients communicate with a local Payment Device Controller through SOAP, JSON, or wizard-like wrappers written in C/C++/Java. The PDC manages terminal communication locally and provides offline store-and-forward capability — transactions are queued when connectivity drops and settled automatically when the connection returns.

Architecture diagram showing client connecting to a local Payment Device Controller, which communicates with the Cloud9 Payment Gateway in the cloud
Local PDC architecture — client connects to PDC locally, PDC relays to Cloud9 gateway

Option 2: Direct Cloud Connection (PWC)

Clients communicate directly with the cloud-based Payment Web Controller (PWC) via SOAP, JSON, or wizard-like wrappers written in C/C++/Java. No local software installation is required — the PWC handles all terminal communication from the cloud.

Architecture diagram showing client connecting directly to the cloud-based Payment Web Controller without local software
Direct PWC architecture — client connects to cloud-based PWC, no local software needed

Payment Device Controller Setup

For detailed hardware configuration and installation steps, refer to the Cloud9 Payment Device Controller Setup documentation provided during onboarding.