New Payment

The New Payment page lets you set up a recurring payment for a customer.

1 How to Use This Page | 2 Detailed Help

An additional feature of the PayTrace Virtual Terminal and the API is the ability to process recurring transactions for any existing customer profile. IIf you wish to process recurring transactions and you are not already signed up for this feature, please contact your Merchant Service Provider or PayTrace Support at Support@PayTrace.com.

How to Use This Page

Click the New Payment link from the Recurring Payments menu.
Select or search for a customer.
Select the email check box if you want a receipt emailed to the customer. Receipts will be emailed to you, the merchant, automatically.
Select the transaction type (Sale or Authorization), then enter the amount to be charged each time.
Select the frequency (Annually, Quarterly, Monthly, Bi-Weekly, Weekly, or Daily) for processing the transaction.
Select a start date (the first time you want the transaction to be charged).
Specify the number of times you want the recurring payment to be processed (999 for indefinite).
Specify an optional recurring payment description.
Click the Save button to save the transaction.

All recurring transactions are processed at 12:30 a.m. Pacific Time on the day that the transaction is scheduled to be processed. Transaction receipts are automatically sent to the email address(es) provided with your PayTrace account each time a recurring transaction is processed. If you already have access to the recurring transactions product, log into your PayTrace account and note the Recurring Payments Menu.

AVS is not required for Recurring Payments, as detailed below:

CPS/Card Not Present—AVS Optional
AVS is not required to qualify for CPS/Card Not Present in the following processing environments:

Non-bill payment transactions utilizing a Health care MCC, a Select Developing Market MCC, or the Utility MCC
For a list of key data requirements in this environment, refer to Table 10–2: CPS/Card Not Present—AVS Optional (Credit or Debit, Mail Order/Telephone Order): Key Data Requirements.
Bill payment transactions
For a list of key data requirements in this environment, refer to Table 10–3: CPS/Card Not Present—AVS Optional (Credit or Debit, Bill Payment): Key Data Requirements.

Bill Payment Transaction
A transaction that results from an agreement between a cardholder and a merchant where the cardholder is billed for goods or services within an ongoing service cycle that is known and agreed upon, in advance, by both the merchant and the cardholder. Transactions may occur monthly or periodically. Such transactions include:

The cardholder initiates single payments in either face-to-face or card-absent environments.
Recurring transactions
Installment billing transactions

Detailed Help

Links

Would you like to create another recurring payment?

Returns you to the Create a Payment page.

Would you like to view a printable consent form?

Opens the Printable Consent Form.

Required Fields

Amount

Input the dollar amount you want to bill this customer regularly.

Start Date

The date on which the recurring transaction was processed for the first time.

Total Count

Enter the number of billing cycles for the recurring transaction. Use 999 for indefinite transactions. PayTrace will process until canceled.

Optional Fields

When creating a recurring transaction, you must first create a customer profile that contains the billing information you want to process recurring payments against.Recurring transactions will be processed overnight on the day that the transaction is scheduled to be processed. A receipt will be emailed to the email address address provided for your account in the PayTrace system.

Customer Profile

Select the customer profile that you want to process a recurring transaction against.

Customer Receipt

Check this check box if you want a receipt emailed to the customer each time the recurring transaction is processed.

Transaction Type

Choose Sale or Authorization. Keep in mind that Sales will automatically settle with the next batch.

Frequency

Select how frequently you want the transaction to be billed.

Annually

Same date each year until the total count is reached.

Quarterly

Same day as the start date each month (e.g., 1/3 - 4/3 - 7/3) in 3-month intervals until the total count is reached.

Monthly

Same day as the start date each month (e.g., 1/3 - 2/3 - 3/3) until the total count is reached.

Bi-Weekly

14-day intervals (e.g., 1/3 - 1/17 - 1-31) beginning with the start date until the total count is reached.

1st and 15th

The first and fifteenth of each month, begin with the start date until the total count is reached.

Weekly

7-day intervals (e.g., 1/3 - 1/10 - 1-17) beginning with the start date until the total count is reached.

Daily

Each day, beginning with the start date until the total count is reached.

Next Date

The next scheduled date that the recurring transaction will be processed is displayed. This date may be changed to any valid date on or after today’s date.

Repeat if declined __ consecutive days

Enter the number of consecutive days/times a declined payment should be retried. Please note that the payment will be processed by its frequency and count settings, regardless of this setting or transaction approval. ** For example: Set a recurring payment that is scheduled monthly to process 12 total times and is scheduled to start on 1/1/2009. If the second transaction (processed on 2/1/2009) is declined, and the user specified that it should be repeated 3 times, PayTrace will process the transaction on 2/2, 2/3, and 2/4, and then again on 3/1. If the transaction attempt on 2/3 was approved, PayTrace will not process the transaction again until 3/1.

Current Count

The current count represents the number of transactions processed per this recurring transaction. The recurring transaction will no longer be processed when the current count equals or exceeds the total count.

Description

Enter your optional comments or discretionary data about the transaction. You may enter up to 255 characters describing the recurring transaction.