Introduction

This documentation aims to aid the understanding of the many modules that composes the solution provided to work with Opayo API. It doesn't replace Opayo's official documentation that can be found here for their API, and here for anything else.

Also, Opayo provides both public accounts for testing here and cards for testing here.

Set-up

To do testing with the demo application please follow what's said below regarding Opayo_IS, other changes/setups won't be changed unless you decide to integrate the modules on your application flow, for this end please do read through the whole setup section.

Opayo_IS

Among the site properties provided, Opayo_Password will be the minimum configuration you'll need to do to use the Demo application. It can be found on their public documentation as mentioned on the introduction section.

If Opayo has provided you with an account, you'll need to set Opayo_VendorName and through their portal you'll need to retrieve both Opayo_Key and Opayo_Password

Payment_FS

This module is an example of middle man to handle requests and responses to and from Opayo, due to this it has a configuration entity with the possible sources that will communicate with Opayo, on this example it has the Sandbox (provided as a Demo app), so in case new sources maybe needed, they can be introduced by changing the resource 'PaymentConfiguration.json' that comes with the module, once replaced with a new version with new sources, it will be bootstrapped if the module gets published.