WEBSTANDARDS Archives

February 2013

WEBSTANDARDS@LISTS.UMN.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Matt Zaske <[log in to unmask]>
Reply To:
UofMN Web Standards <[log in to unmask]>
Date:
Mon, 18 Feb 2013 18:02:35 -0600
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (2147 bytes) , text/html (3480 bytes)
I have been involved with projects where both aforementioned products have
been used.  In my opinion, the authorize.net system provides a more
seamless experience for the end user (and there were no PCI compliance
issues with that integration since _all_ transactional processing was
handled elsewhere based upon our configuration).

I can't speak to the financial transaction (e.g. payment from the vendor)
side of things but I'd recommend authorize.net first, regonline second.

--Matt

On Mon, Feb 18, 2013 at 5:18 PM, Karen Anderson <[log in to unmask]> wrote:

> My organization, Center for Early Education and Development (CEED), uses
> Regonline (http://www.regonline.com). We are very happy with it. They
> have free trainings that you can attend online to get you started. You have
> many options (easy and advanced) for how to set up a registration form.
> Good help line. Depending on what plan you choose, there is a per
> registrant fee plus a credit card fee, but I think that's fairly standard
> across registration systems. We are very happy with it.
>
>
> On Mon, Feb 18, 2013 at 4:23 PM, Christopher Bongaarts <[log in to unmask]>wrote:
>
>> On 2/18/2013 2:35 PM, Marshall, Kirk wrote:
>>
>>> Have any of you in the Web Standards group worked with these or other
>>> providers to set up online payment on a U website? What would you
>>> recommend?
>>>
>>
>> Way back when we used to charge for email account upgrades, we used
>> Cybercash, which was bought and merged into Surepay, and then we ditched
>> online payment altogether.
>>
>> Last I heard the recommendation was for Authorize.net.  Since using any
>> payment service usually involves some coding (or at least used to), you may
>> find more answers on the code-people list.
>>
>> Watch out for PCI compliance issues (which may vary by vendor or
>> integration type).
>>
>> --
>> %%  Christopher A. Bongaarts   %%  [log in to unmask]          %%
>> %%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
>> %%  University of Minnesota    %%  +1 (612) 625-1809    %%
>>
>
>


-- 
Matt Zaske
Web App Developer/Windows Server Admin
Computing Services
University of Minnesota, Morris
10 Behmler Hall, 600 E 4th St
Morris, MN  56267
320-589-7017


ATOM RSS1 RSS2