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) is crossed.
Payment gateway requests are further processed using WEB APIs and sent to 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. Requests cannot be processed further and do not have a Data Entry page.
Payment gateway requests fields
The table describes the fields of the Gateway Summary page and explains how the fields are used.
Number | An auto-generated unique ID for each gateway request. |
|---|---|
| Payment Gateway Provider | Processes the gateway request |
| Type | 'Payment', 'Refund' or 'Payment Cancellation'. |
| Payment Gateway Run | The processing run that automatically created the request. |
| Payment | The number of the refund created in CRM.COM. |
| Payment Cancellation | The number of the payment cancellation created in CRM.COM; applies to generic payment providers only. |
| Payment Gateway Reference Number | The number provided by the payment gateway. The number is assigned when a request is 'Posted' or 'Rejected' and therefore not available for requests in other life cycle states. |
| 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.
|
| Execution Date | The date on which the request was posted or rejected by the payment gateway provider. |
| Life Cycle State | Requests can be in one of the following states:
'Pending' or 'Under Processing' requests can be rejected or posted through WEB APIs. |
| Error Code | Received by the payment gateway provider, in case of error. |