PaymentInfo/AutomatedPayment - Revision history

Scarpenter: Replaced content with "=This Content Has Moved House= This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. We are sorry for the unti..."

2020-04-22T02:17:36Z

Replaced content with "=This Content Has Moved House= This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base. We are sorry for the unti..."

Show changes

Dcowan: added link to Emersion Support article

2018-07-24T02:26:58Z

added link to Emersion Support article

Scarpenter: /* Automated Payment */

2018-07-24T02:03:10Z

‎Automated Payment

Scarpenter at 02:02, 24 July 2018

2018-07-24T02:02:48Z

Dcowan: minor textual correction given current environment

2018-03-27T05:43:07Z

minor textual correction given current environment

Dcowan: fixed the YEARS old 10am daily statement. surprised nobody bothered to change this some time ago

2017-04-24T01:32:51Z

fixed the YEARS old 10am daily statement. surprised nobody bothered to change this some time ago

Rlusher: /* Introduction */

2014-06-23T06:30:18Z

‎Introduction

Rlusher: /* Introduction */

2014-06-23T06:29:51Z

‎Introduction

Rlusher: /* Introduction */

2014-06-23T06:04:41Z

‎Introduction

Rlusher: /* Automated Payment */

2014-06-23T06:04:24Z

‎Automated Payment

@@ Line 26: / Line 26: @@
 * Days between each retry. The minimum is 1. 0 and negative values are not supported.
-Please contact Emersion Support to implement different default values for your service provider account. These values cannot be overridden at the customer or end user account level. Overrides of these values replaces the system default with your own default.
+Please contact [https://resources.emersion.com/display/EKB/Support+and+Help+from+Emersion Emersion Support] to implement different default values for your service provider account. These values cannot be overridden at the customer or end user account level. Overrides of these values replaces the system default with your own default.
 === Automated Payment Configuration ===

@@ Line 26: / Line 26: @@
 * Days between each retry. The minimum is 1. 0 and negative values are not supported.
-Please contact Wmersion Support to implement different default values for your service provider account. These values cannot be overridden at the customer or end user account level. Overrides of these values replaces the system default with your own default.
+Please contact Emersion Support to implement different default values for your service provider account. These values cannot be overridden at the customer or end user account level. Overrides of these values replaces the system default with your own default.
 === Automated Payment Configuration ===

@@ Line 16: / Line 16: @@
 * Generate a payment. (Notes: if the payment method is credit card, we need to get credit card sub-type from EPS, which may cause payment failure.)
-<br />
+System default rules:
-'''The rules around retry attempts and frequency are as follows:'''
+* For Automated Credit Card Payments, the system will retry to process the credit card details 3 times before disabling the payment method.
-* For Automated Credit Card Payments, it will retry the credit card details three times, once per day, before disabling the payment method in the event of three unsuccessful retries.
+Service providers can choose to have the following system defaults overridden:
-* For deduction from a bank account, it will only accept one failure before disabling the payment method.
-<br />
+* Maximum number of retries
-----
+* Days between each retry. The minimum is 1. 0 and negative values are not supported.
 === Automated Payment Configuration ===

@@ Line 161: / Line 161: @@
 {| border="1" style="border-width: 1px; border-style: solid; border-color: #000; padding: 0"
-|+ <u>Bpay Input Validation</u>
+|+ <u>BPAY Input Validation</u>
 ! Field !! Validation
 |-
 |style="width:25%"| Biller Code || This is a drop down list of values you have previously defined. You can set/add Biller Codes by navigating to <code>Home > Bpay Biller Code and clicking 'Create New Biller Code'</code>.
 |-
-|style="width:25%"| Reference || This field accepts a numeric value that will be used to uniquely identify BPay payments from your customer.
+|style="width:25%"| Reference || This field accepts a numeric value that will be used to uniquely identify BPAY payments from your customer.
 |}
-Bpay Reference Numbers can also be auto generated per customer. Instead of entering a custom Reference Number, click the "Auto Generate" button and the Emersion system will automatically generate and insert a reference number for you. Currently, we use the 6 digit customer account number, run the account number through the Luhn algorithm to generate a single check digit at the end of the account number & then pad it with an extra 0 at the beginning.
+BPAY Customer Reference Numbers can also be auto generated per customer. Simply select an alternate biller code and the Emersion system will automatically generate and insert a reference number for you. Currently, we use the 6 digit customer account number, run the account number through the Luhn algorithm to generate a single check digit at the end of the account number & then pad it with an extra 0 at the beginning.
-Example: Account Number '''101897''', run through Luhn generates '''7''' as a check digit. Add a 0 to the beginning and the reference number will become '''01818977'''. (Emersion may, in the future, provide support for customised digit padding & algortihm choice for Bpay Reference Number auto generation)
+Example: Account Number '''101897''', run through Luhn generates '''7''' as a check digit. Add a 0 to the beginning and the reference number will become '''01818977'''. (Emersion may, in the future, provide support for customised digit padding & algorithm choice for BPAY Reference Number auto generation)
 Finance Charges are the same [[PaymentInfo/AutomatedPayment#automatedpayment_charges|as above]].

@@ Line 5: / Line 5: @@
 For customers who are signed up for the Emersion Payment System (aka '''EPS'''), automated payment details may be configured on a per-customer basis.
-At 10am daily, our '''AutomatedPayment''' process runs and acts on all of your children accounts based on a set of criteria being met. For each account that has valid automated payment info, '''AutomatedPayment''' executes the following steps:
+On a regular basis throughout the day, our '''AutomatedPayment''' process runs and acts on all of your children accounts based on a set of criteria being met. For each account that has valid automated payment info, '''AutomatedPayment''' executes the following steps:
 * Check if the current account has an incomplete payment. If it has an incomplete payment, exit. Incomplete payments are listed as a ''Pending Payment'' in the Cumulus UI.
@@ Line 20: / Line 20: @@
 '''The rules around retry attempts and frequency are as follows:'''
-* For Automated Credit Card Payments, it will retry the credit card details three times, once per day, before disabling the payment method in the event of  three unsuccessful retries.
+* For Automated Credit Card Payments, it will retry the credit card details three times, once per day, before disabling the payment method in the event of three unsuccessful retries.
 * For deduction from a bank account, it will only accept one failure before disabling the payment method.
 <br />

@@ Line 21: / Line 21: @@
 * For Automated Credit Card Payments, it will retry the credit card details three times, once per day, before disabling the payment method in the event of  three unsuccessful retries.
-* For deduction from a bank account, it will try only once, before disabling the payment method.
+* For deduction from a bank account, it will try only once, before disabling the payment method.  One failure will be enough to trigger disabling of this payment method.
 <br />
 ----