PPI: Difference between revisions

From NewHaven Software Wiki
Jump to navigationJump to search
Russ horton (talk | contribs)
New page: Payment Processing Inc. Competitor of MPS that we are considering for payment processing/gateway. Pros *Member of the PCI council *Develop and support their own gateway (24/7 support) *W...
 
Russ horton (talk | contribs)
Removing all content from page
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Payment Processing Inc.


Competitor of MPS that we are considering for payment processing/gateway.
Pros
*Member of the PCI council
*Develop and support their own gateway (24/7 support)
*Will pay for our PA DSS and visa listing if we adopt their tokenization solution
*Experienced staff of compliance guys who work closely with QSA's and they can get us the answers we need
*Work with us to pre-assess
*Reduced recert ~3K (every 3 yrs)
Cons or challenges
*If we adopt tokenization, we must convert all users onto it - PPI would be our only provider
**Can run a batch process to get tokens for existing cards when we first convert
*Not compatible with other gateways
*uses order number as unique identifier (must be integer, no alpha or dashes)
**allows us to poll their system for the status of a charge (if we lost connection)
**They can provide an order number (like a transid) since there are too many obstacles to us using order number (cv3, multiple invoices per order, multiple credit cards for an order, alpha)

Latest revision as of 23:53, 28 October 2009