To configure a custom payment gateway, you will need the configuration parameters from the payment gateway provider you have chosen. These parameters must be entered in School Software Pro and will be used to map to that particular gateway provider. Though configuration parameters slightly differ for each gateway provider, parameters of most gateway providers can be commonly grouped based on the following parameter types:
- Configuration Fields – Configuration parameters will remain constant for all transactions for a merchant through a particular gateway. These parameters must be created in name-value pairs in the custom gateway creation page. It includes the merchant credentials such as merchant ID, transaction password, currency etc., which is sent to the gateway to authenticate the merchant for a transaction. Along with these parameters, the parameter ‘target_url’ must also be created. This parameter specifies the URL to which the payment form will be sent.
Mandatory configuration parameter: ‘target_url’ - Variable Fields – Variable parameters will vary for each transaction. Example of variable parameters are, amount, redirect URL, item name etc. Variable parameters must be created in name-parameter_type pairs in the custom gateway creation page. Parameter types are predefined in School Software Pro and must be specified. Only one parameter name is allowed for each parameter type.
Mandatory variable parameter: ‘Amount’, ‘Redirect URL’ - Response Parameters – As the name indicates, response parameters are the responses that will be sent by the gateway to the user after a transaction is processed. Just like variable fields, response parameters must also be created in name-parameter_type pairs.
Mandatory response parameters: ‘Amount’, ‘Success Code’, ‘Transaction Status’, ‘Transaction Reference’
Payment Processor: Except for PayPal, the other six payment gateways that School Software Pro supports requires a payment processor to process debit/credit card information and execute the online transaction. For this purpose, School Software Pro uses its own ‘Payment Processor’. If integrating a payment gateway—other than the seven that School Software Pro supports—that requires a payment processor, you will have to use your own payment processor or source it from a third party.