PaymentGatewayProvider configuration
The PaymentGatewayProvider configuration defines gateway providers that can be used for payment processing in the Cashiering module.
The root
node can have these attributes:Attribute | Description |
---|---|
Credit Card Validation | Indicates whether Infor Operations and Regulations will validate the card number entered for a credit card transaction before adding the transaction to the database. A checksum algorithm is used to validate the card number. Note that this doesn't ensure that the card number matches the card type. You can use the Credit Card Type Validation attribute for that. If set to True, Infor Operations and Regulations will show an error message and won't add the transaction when an invalid card number is entered. If False, Infor Operations and Regulations will add the transaction, but will then reverse the transaction and decline the payment if the card number is invalid. Note that you can also use a BeforeAdd formula to validate the card number, either in addition to or instead of the checksum algorithm. |
Credit Card Type Validation | Indicates what Infor Operations and Regulations will do if the first digit of the card number entered for a credit card transaction doesn't match the card type (such as 4 for Visa). You can specify one of these values:
|
Two Stage Portal Transactions | Set to True to enable two-stage processing of payment transactions.
This is typically used for payments submitted through third-party gateways. In the first stage, a pending transaction is created. In the second stage, the transaction is completed after an authorization is returned. |
The
node has multiple nodes as children. Each node has these attributes:Attribute | Description |
---|---|
Moniker | Moniker of the gateway provider. This is the moniker of the object that contains the AuthorizePayment and ReversePayment methods. |
ProviderName | Name of the provider. This name is displayed in the Payment Sever Gateway list in Cashiering Setup. |