Paul (12/5/2005)

---

The current version of the Gateway is the Original.  It was launched in early 2002 and  has been added to with enhancements, new features, and modifications, and has evolved to its fullest safe potential.

With a long list of new features, enhancements, and capabilities we set out to redisign the system for multiple reasons, the least of which was not safety.  By safety I mean stability.

Because of the programming language used and the database design of the current platform adding to it is very laborious, and growing volume will surely bring us to errors and bottlenecked processing eventually.

We also started licensing the platform to financial institutions and other companies in 2004 and creating a private label version takes quite a few days.

There are, as I mentioned, many more reasons but there is no reason to go into them.

Version 2.0 is basically the functionality and reporting of the current version, but totally redesigned from the ground up to enable clean and stable additions, modifications and enhancements.

It also makes creating a licensed private label system much easier to accomplish.

Once 2.0 is rolled out we will begin adding the enhancements and features, and the list is long, plus we are open to requests and suggestions.  If it makes sense we are happy to  include it.

The change in security is the result of the new design.  It didn't make any sense to try to leave the old selector box type security in the new design, and with the extension of parent/child relationships like sub-merchants, operators, etc., we built into the new design a way to maintain parent/child infinitely with highly granular security, using roles and permissions.

More later .....

Paul (12/17/2005)

---

As I was saying,

Security is greatly enhanced in 2.0 not only from our standpoint as a processor, but additionally for the client.

No longer will the Merchant Admin create an Operator, then select Operator Permissions in the selector boxes.  Instead, the Merchant Admin will now create Roles.  Once a Role is created it can be assigned to multiple Operators, and Operators can have multiple Roles.

For example;

Let' say a merchant needs customer service staff to view transaction activity to look up items sent to customer accounts.

So the Merchant Admin creates the Role "Customer Service".  Next permissions are assigned as seen in the screen shot below.

Now the merchant has to create the operator accounts and assign the role.

Paul (12/17/2005)

---

Creating the operator account is a breeze.  Using a dollar limit won't mean anything with the permissions assigned in the Cusotmer service role as there is no permission to create a transaction or refund.

Now the Merchant Admin needs to go back and assign the role to the Operator.

Paul (12/17/2005)

---

So the Operator assigment offers the choices as follows;

Paul (12/17/2005)

---

And the Merchant Admin simply highlights the Customer Service Role and assigns it.

Now the Operator has those permissions.

But as I mentioned earlier, Operators can have more than one role so let's say Oliver here is a customer service manager and needs to be able to do refunds also.