Index of /

# Paygate Integration ## Configuration The integration can be configured via the config.ini.php file. The client must register with PayGate and set up their account on the Merchant Portal (https://map.paygate.co.za/login.php). Here they will find their PayGate ID and an Encryption Key / Secret. Additionally, they must supply an email address for receiving the payment confirmations of the transactions. These must be added to the config file under the *customer* section. ### Website Integration There are three config settings required for the integration: - finaliseUrl: This is used at the completion of the transaction to redirect the user back into the website. A confirmation of the transaction can then be displayed. - integrationClass: A class with a specific structure which the paygate system will use for storing and retrieving reference data associated with the transaction. - integrationClassFile: The file path and file name of the file containing the integrationClass. ## Logging The log directory is set as *Paygate/logs*. If required, a different directory can be configured via the config file under the *general* section. Once the directory has been configured it must be set to be writeable by the server. The log level can be configured in the config file. There are three levels of logging: ERROR, INFO and DEBUG. ERROR: only errors will be logged. INFO: errors and some informational messages will be logged. DEBUG: everything will be logged. Only use for development purposes. ## Style The views contained in *Paygate/views* can be styled to fit in with the rest of the website. paygate.view.php is used to redirect the user to the PayWeb UI. A spinner can be added here to indicate activity to the user. finalise.view.php is the final confirmation page displayed to the user. This can also be used as a redirect back into the website. ## Workflow / Process STEP 1: Submit & store the payment information - display Example index.php page. STEP 2: Pass the payment information to the PayGate integration - via the iFrame. STEP 3: PayGate PayWeb will display payment options via the iFrame and process the transaction. STEP 4: PayGate PayWeb will return the transaction response data via the notifyUrl - this is received and processed without user interaction. STEP 5: PayGate PayWeb will redirect the user back into the website - via the returnUrl. In the case of an EFT or other non-immediate payment (asynchronous process): STEP 6: Upon completion of the payment, PayGate PayWeb will return the transaction response data via the notifyUrl - this is received and processed without user interaction. ## Example Everything required by the website is laid out in the example. This can be used as a basis for integrating the system into the website. The most important aspect is to ensure the existence and structure of the integrationClass and ensure the config.ini.php file is updated.