Skip to end of banner
Go to start of banner

Creating and processing Generic Gateway Requests (Included page)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Finance > Payment Gateways > Perform Automatic Payment Runs


As mentioned above, payment gateway requests may be created as soon as a payment, refund or payment cancellation is created in CRM.COM, and is associated with the Payment Gateway either through its type or method.
Automatic payment runs on the other hand are used to identify bills that should automatically be paid or wallets that should be automatically topped up via a Payment Gateway. 

 

Bill Payment: Unsettled bills can be directly paid by payments made to the payment gateway. In this way, a bill is always handled before it is due, without the customer worrying whether the payment has been made. This functions like a Direct Debit, which in this case is electronically handled via a payment gateway. The Automatic Payment Run will create payment requests fir every identified bill that meets the conditions below

Wallet top up: Make a request to automatically top up your prepaid subscriber's wallets through their online accounts and ensure that their subscriptions will never be interrupted.  The available functionality detects whether the wallet balance has fallen beneath a certain threshold, in which case the system automatically creates a payment request, to top-up the wallet, to the Payment Gateway the customer is registered with.

To enable wallet top-up, configure the top-up rules in the active wallet definition, where you can define the minimum amount the wallet should have for the top up to be triggered, the amount of the top up, and how often the check should be done. Once the system is setup, it is up to the Automatic Payment Run to create payment requests for every wallet that meets the following prerequisites:


Navigate to Automatic Payment Runs and specify the gateway provider you would like to create requests for, as well as the scheduling information. Once completed SUBMIT the run to create the requests.

 Mandatory   Configurable

Main Information

Life Cycle State: The life cycle state of the automatic payment run definition. The state must be set to 'Effective' to be able to execute a run.

Payment Gateway Provider: The provider that will be used to execute the Run. Only 'Effective' Payment Gateway Providers can be selected.

Process Runs
Includes the standard Process Run Information related to the processed requests.

 

 

 BillsWallets
Prerequisites

'Unsettled' or 'Partially Settled' Bills that belong to Accounts Receivables with a Payment Preference which is processed by the payment gateway and have the "Use for Recurring Payments" setting enabled.

  • Wallets whose associated accounts receivable classification is included in the Wallet Definition's "Auto Top Up Rule" and which have a 'payment preference' which is processed by the payment gateway and have the "Use for Recurring Payments" setting enabled
    AND 
  • Wallets whose balance is equal to or less than the specified balance threshold
    AND
  • Wallet's whose "Latest Auto Top-Up Date" is empty or before than or equal to the date of execution minus the specified "frequency in days" set in the Wallet Definition
PostconditionsIf a 'Pending' or 'Under Processing' Payment Request exists for the identified Wallet to be topped up or for the Bill to be paid, then the Request will not be created, in order to avoid duplication of Payment Requests.
  • No labels