Creating and processing Generic Gateway Requests (Included page)

Finance > Payment Gateways > Perform Automatic Payment Runs

Payment gateway requests are created when payments, refunds or payment cancellations (associated with the gateway through their type or method) are created in CRM.COM.
Additionally, automatic payment runs identify bills to be paid or wallets that should be automatically topped up through a payment gateway. 

Bill Payment: Unsettled bills can be paid through the payment gateway before they are due, sparing the customer of the anxiety associated with its timely payment. The process is similar to a direct debit transaction.  The automatic payment run identifies bills that meet predefined criteria and creates the respective payment requests.

Wallet top-up: Requests can be used to automatically top-up the wallet of prepaid subscribers from their online accounts, ensuring that the service is not interrupted.  The system detects when the wallet balance crosses a predetermined threshold and automatically creates a top-up request through the customer's gateway.

To enable wallet top-up, configure the top-up rules in the active wallet definition.  Define the threshold that triggers top-up, the amount to credit the wallet and frequency at which the balance should be checked. Once the system is set up, the automatic payment run will create payment requests for wallets that meet predefined criteria.

To create an automatic payment run, navigate to Perform Automatic Payment Runs and create a NEW definition. Select a gateway provider, supply scheduling settings and SAVE. Once completed SUBMIT the run to create the requests. 

Automatic Payment Run Definition fields

 Mandatory   Configurable

Main Information

The Life Cycle State of the automatic payment run definition must be set to 'Effective' to execute a run.

Only 'Effective' Payment Gateway Providers can be selected to execute runs.

Process Runs
Process Run Information related to processed requests.

 

Additional information

Bill Prerequisites
  • Must be 'Unsettled' or 'Partially Settled'.
  • Must be associated with an accounts receivable with a payment preference processed by the payment gateway.
  • Must have the 'Use for Recurring Payments' setting enabled.
Wallet Prerequisites
  • Must be associated with an accounts receivable whose classification is included in the Wallet Definition's 'Auto Top-Up Rule'.
  • Must be associated with an accounts receivable with a payment preference processed by the payment gateway.
  • Must have the 'Use for Recurring Payments' setting enabled
    AND 
  • Must have a balance up to the specified threshold
    AND
  • 'Latest Auto Top-Up Date' field is blank or up to the date of execution minus the specified 'Frequency (in Days)' set in the Wallet Definition. 
PostconditionsIf a 'Pending' or 'Under Processing' payment request already exists for the wallet identified for a top-up or for the bill to be paid, then the request will not be created (to avoid payment request duplication).