Payment Gateway's integration, primary purpose is to handle requests created through manual and automatic processes in CRM.COM to ensure payments and refunds from and to customer's online accounts and CRM.COM are possible.
Requests are created either whenever a payment, refund or payment cancellation of supported methods and types defined in the provider, is manually created through Financial Transactions; additionally requests are created whenever the Payment Gateway Run is executed in the system which will create requests in 2 occasions:
...
Integration with a payment gateway enables the handling of payment and refund requests between CRM.COM and online accounts belonging to customers.
Requests are triggered when payments, refunds or payment cancellations, using methods and types supported by the provider, are manually created in the financial transactions Data Entry page.
Payment gateway runs also create requests to:
- Settle outstanding bills, subject to the payment preferences of the account.
- Top up wallets that fund prepaid subscriptions when the wallet's threshold (set in CRM.COM) and must be topped up, so that there are enough funds in the wallet for paying for prepaid subscriptionsis crossed.
Payment gateway requests must then be are further processed using WEB APIs in order to be and sent to the specific Payment Gateway and updated accordingly. i.e. completed or rejected. the gateway. The life cycle state of the request is updated to 'Posted' or 'Rejected', accordingly.
All requests are available through a dedicated Summary page. No further manual handling is allowed, and therefore requests Requests cannot be processed further and do not have a Data Entry page.
Payment
...
gateway requests fields
The table describes the fields of Summary page, the Gateway Summary page and explains how the fields are used.
Number | An auto-generated number that uniquely identifies each payment unique ID for each gateway request. | ||
|---|---|---|---|
| Payment Gateway Provider | The payment gateway provider that will process the payment Processes the gateway request. | ||
| Type | The type of the request which can be any between: 'Payment', 'Refund' or 'Payment Cancellation'. | ||
| Payment Gateway Run | The payment gateway processing run that automatically created the request, if it was created automatically. | ||
| Payment | The payment number of the refund created in CRM.COM. | ||
| Payment Cancellation | The payment cancellation number of the payment cancellation created by in CRM.COM This information is applicable only if the payment gateway provider is a generic payment gateway provider; applies to generic payment providers only. | ||
| Payment Gateway Reference Number | The payment gateway request reference number as provided by the payment gateway.
| ||
| Account Number | The number of the accounts receivable number associated with the payment gateway request. | ||
| Paid Bill | The number of the bill that was paid or is intended to be paid. | ||
| Topped-up Wallet | The number of the wallet that was topped-up. Wallet information is always set even if a payment is not created and available only if the payment was created in order to top up a Wallet.
| ||
| Execution Date | The date on which the request was posted or rejected by the payment gateway provider. | ||
| Life Cycle State | The life cycle state of the payment gateway request which can beRequests can be in one of the following states:
'Pending' or 'Under Processing' payment gateway requests can be rejected or posted through WEB APIs. | ||
| Error Code | The error code received Received by the payment gateway provider, in case of an error. |