One of the main reason
for using our payment gateway and the processing servers is the
integrated recurring billing system with full management through
the Administrative interface.
Payment Online's recurring system has unmatched functionality and
feature-set for a platform of its type. Which receives constant
addition of features and functionality to remain years ahead of
competition.
Below we have provided for you some of the flexible implementations
that our customers have adopted to cater for their business model
or marketing strategy.
For any recurring transaction, there are always 3 fields that are
required. They are recur_billing,
bill_cycle, and num_cycles.
These are the minimum needed to process a recurring transaction.
There are many other optional fields, the use of which depends on
what type of recurring billing implementation you desire.
See product fields in our sample (subscription) product setting
below:
Here are some sample implementations that our clients have chosen.
However, there are many different implementations that are not included
here. Please ask our sales professionals for additional details.
Implementation 1 - Payment Gateway
Suppose that you want to charge a customer $30.00 per month on
the 1st of every month for 12 months. You also, want to pro-rate
their initial billing to the first billing date (1st day of the
coming month). Here's sample variable settings.
| FIELD |
VALUE |
recur_billing |
1 |
bill_cycle |
1 month |
recur_bill_amount |
Empty |
num_cycles |
11 |
first_billing_date |
Empty |
recur_bill_day |
1 |
prorate_first_billing |
1 |
Implementation 2 - Payment Gateway
Suppose that you want to charge a customer $10.00 for the first
month, and $30.00 per month thereafter for 11 months, you would
set the following values:
| FIELD |
VALUE |
recur_billing |
1 |
bill_cycle |
1 month |
recur_bill_amount |
30 |
num_cycles |
11 |
first_billing_date |
Empty |
recur_bill_day |
Empty |
prorate_first_billing |
Empty |
| item_price |
10 |
Implementation 3 - Payment Gateway
Suppose that you give your customers a free 15 day trial, authorize
the card for one dollar to make sure it is valid but don't 'capture'
the fund. You also want to automatically bill them thereafter at
$29.95 per month until they cancel.
| FIELD |
VALUE |
recur_billing |
1 |
bill_cycle |
1 month |
recur_bill_amount |
29.95 |
num_cycles |
999 |
first_billing_date |
15 days |
recur_bill_day |
Empty |
prorate_first_billing |
Empty |
| item_price |
1.00 |
| trans_type |
AUTHONLY |
Implementation 4 - Payment Gateway
You may want to give your customers a free trial through the end
of the current month (no authorization), and bill them $14.95 monthly
on the 1st of the month every month thereafter until they cancel.
| FIELD |
VALUE |
recur_billing |
1 |
bill_cycle |
1 month |
recur_bill_amount |
14.95 |
num_cycles |
999 |
first_billing_date |
Empty |
recur_bill_day |
1 |
prorate_first_billing |
Empty |
| item_price |
1.00 |
| trans_type |
NOAUTH |
These are only some of the few implementations that are most popular.
There are many other implementations of recurring billing models
possible thanks to the flexibility of this powerful payment gateway.
The Payment Online's Payment Gateway automatically populate the
username and password
fields that are sent in the POST Back.
As default. the username is usually the email address of the customer
which customers can easily remember, and the password is a random
generated code.
This is done for every order even if it is not used, so it is always
available via the Post Back. Either one or both of these fields
can be overridden if they are sent along with the transaction.
If you place a value in the username or password field and submit
it with the transaction, the recurring
management system will use the values you send instead
of the default ones generated internally.
To add the username and password to your authentication database,
the POST Back feature can be used which performs an http POST to
a cgi script on your website with the username and password, along
with other information.
In order to make sure that not just anyone can POST a new user
to your database, there are mechanisms in place that sends notification
when this occurs.
How you handle authentication of
users is entirely up to you and the decision on
how http authentication should be implemented is up to you and your
Webmasters or programmers.
Payment Online provides cgi scripts for various systems that can
be used to accept the POST back and add the username and password
to your database, but configuring your system and installing the
script is undertaken by your staff.
|
Contact
Payment Online's customer care department at (206)
382-1515 - option "3",
and request to sign up.