Back to Generic Gateways Main Page
Learn to set up Generic Payment Gateways related business processes and rules.
Mandatory Configuration: Links to manuals of Generic Payment Gateways configuration modules that are required for the module to work correctly
Related Configuration: Links to manuals of configuration modules other than the Generic Payment Gateways's that offer additional functionality or are required for the module to work correctly
Optional Configuration: Links to manuals of Generic Payment Gateways configuration modules that offer additional functionality but are not required for the module to work correctly
Mandatory Configuration
The following modules must be configured in order to use the Generic Payment Gateways:
| Module Name | Manual | Description |
|---|---|---|
| Payment Gateway Provider | Configuring Payment Gateway Providers | Define attributes related with each Payment Gateway such as the supported Payment Methods, Currencies and Preferences |
Related Configuration
The following modules are related to, but are not a part of, Generic Payment Gateways. Such entities either:
- Must be configured accordingly in order to be able to start using the Generic Payment Gateways module (Configuration Type = Mandatory)
OR - May be configured to use the Generic Payment Gateways module at its full capacity (Configuration Type = Optional)
| Module Name | Module Manual | Module Description | Configuration Type |
|---|---|---|---|
Financial Transaction Payment Methods | Configuring Payment Methods | Create a payment method that will be used to identify payments that need to be handled by a Generic Payment Gateway. The Payment Method created above should be added to Provider Payment Methods. In this way the System will know that any payment made with the specific Payment Method, it will be handled by the specific Gateway | Mandatory |
| Financial Transaction Types | Financial Transaction Types | Configure different Financial Transaction Types for Payment and Payment Cancellation Classification to easily identify them. The Payment Cancellation Payment Type must then be added to Provider Payment Cancellation Causes. In this way the System will know that any Payment Cancellations of these type must be handled by the specific Gateway | Optional |
| Accounts Receivable Payment Preferences | Payment Preference | Configure Payment Preferences that will be related to a specific Payment Gateway and will be used when registering an Accounts Receivable and making a Payment for that account that should be handled via the Payment Gateway | Mandatory |
| Accounts Receivable Classifications | Accounts Receivable Classification | Configure Classifications that can be used in the Wallet Definitions Auto Top Up Rules | Optional |
| Wallet Definitions | Wallet Definitions | Configure Auto Top Up Rules if you would like the Wallet to be automatically topped up | Optional |
Optional Configuration
The following entities are available and can be configured under Generic Payment Gateways. A working CRM.COM model can exist without them being configured.
| Module Name | Module Manual | Module Description |
|---|---|---|
| Automatic Payment Run Definitions | Automatic Payment Run Definitions | Used to identify unsettled bills, wallets that need Top-up and payments that have been cancelled and create Payment Gateway Requests |