Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Payment Processing Basics

Avatar for John Suder John Suder
September 27, 2011

Payment Processing Basics

Learn the basics of electronic payment processing. A recent Tech Talk at Pivotal Labs in NYC presented by Robert Brodie, Head of Technology Experience at SUMO heavy Industries.

Avatar for John Suder

John Suder

September 27, 2011
Tweet

Other Decks in Programming

Transcript

  1. Cardholder The cardholder approaches the merchant and wants to purchase

    goods and/or services. They present their card to the merchant.
  2. Merchant The merchant needs to find out if the cardholder’s

    account can be charged for the amount they want to spend, so they need to ask the Issuing Bank for authorization.
  3. Payment Gateway The merchant sends information to the Payment Gateway

    through an API or device. The Payment Gateway then communicates with the issuing bank.
  4. Issuing Bank • The issuing bank will attempt to authorize

    the cardholder’s account for an amount specified by the merchant. • This authorization is held for 1-5 days. (Some banks allow 30) • Once authorized, the merchant can capture at any time prior to the expiration of the authorization.
  5. Settlement Settlement occurs every night when the issuing bank transfers

    captured funds to the acquiring bank. This connection occurs through a payment network.
  6. Network Security • Work with your host or IT team

    to create a secure environment. • Set up a firewall • Never use default passwords
  7. Protect Cardholder Data • Develop an encryption scheme • Encrypt

    all data transmission across public networks
  8. Access Control • Limit cardholder access to data to only

    the people who need it • Assign unique logins to all users • Restrict physical access to cardholder information
  9. Network Monitoring • Create audit trails within your system •

    Create a plan to implement continuous testing and patching (software updates are released for good reasons)
  10. Level 4 Businesses processing less than 20,000 eCommerce transactions and

    less than 1 million other transactions per year. These businesses must complete a yearly risk assessment using one of the PCI Self-Assessment Questionnaire (SAQ) forms.
  11. Level 3 Businesses generating between 20,000 and 1 million transactions

    per year require an annual risk assessment using one of the SAQ forms.
  12. Level 2 Businesses generating between 1 million and 6 million

    transactions annually. A PCI SAQ must be completed every year.
  13. Level 1 Businesses generating a minimum of 6 million transactions

    per year must conduct an annual internal audit with a qualified PCI auditor.