Since you already have Authorize.net, why not just use them? Use their
APIs to process the request. We do that now with our utility bills. We
have a program that uses our processors (horrible) APIs to send the
payment information to them. They then return to our program approved
or denied. We log the transaction in the database and mark them as
paid. We take in the CC # and pass it to the processor. We don't log
or touch it after that. We still have to follow the PCI rules (though
at our level, they are quite simple).

--
Mike Wills
http://mikewills.me



On Thu, Jun 2, 2011 at 1:39 PM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx> wrote:
This is a catchall response to everyone who has chimed in so far.

These are businesses paying us, not individuals.  Some customers asking for
this are probably thinking about credit cards ("CC") and other customers
some kind of online bill pay outside of CC.  We do have a few customers
paying us with their bank's bill pay, meaning we receive a paper check in
the mail as a result.  From the customer's standpoint, this seems to me to
be about the same thing as online from our website, doesn't it?  Maybe other
customer's banks don't have this bill pay, or it costs, or the customer is
unaware of it.

We currently accept CC (Visa & MC) and enter them online via authorize.net.
 We get a bill monthly from North American Bancard.  We average about 25
transactions (or less) per month from *maybe* a half-dozen customers using
it.  So there's virtually no automation at all on our side to handle this.
 One transaction a day does not warrant it.  After the initial entry, we
never see the customer's credit card.  We enter the payment manually, not
the customer.  We also do not promote customers using CC because of the fees
that get charged.  The food distribution industry margins are razor-thin to
begin with.

I do not know how the transaction volume might change if we offered
something like this on our website.

Does the Google route handle credit cards and bank transfers?  If so, then
any customer could pay by CC at any time, could they not?  And we would
never see the actual CC.



On Thu, Jun 2, 2011 at 2:11 PM, Jerry C. Adams <midrange@xxxxxxxx> wrote:

Jeff,

What kind of customers are you talking about?  By that, I thought that your
company sold to business accounts as opposed to individuals.

Individuals use things like PayPal and credit cards in my view.  The
company
for which I used to work paid many of its vendors with electronic funds
transfers (EFT).  I never got involved in the details as it never hit our
System i directly, but I would think that your bank could explain the
details.

Jerry C. Adams
IBM i Programmer/Analyst
"Some cause happiness wherever they go; others, whenever they go." -Oscar
Wilde
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Wills
Sent: Thursday, June 02, 2011 12:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Customers pay us online

You'll need someone to process credit cards. Paypal, Google,
Authorize.Net, and many, many more do that. Depending on who you go
with and how you process it, you may need to be concerned with PCI
compliance.

--
Mike Wills
http://mikewills.me



On Thu, Jun 2, 2011 at 11:31 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:
A few customers have expressed interest in paying us online.  What's
involved in this?

Is there normally an intermediary involved, like PayPal?

Thanks.

--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of
my company.  Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].