Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Accepting Online Payment for Your Library and ‘Stripe’ as an Example

Presentation given at Code4Lib DC Unconference, Aug. 11-12, 2014.

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

Accepting Online Payment for Your Library and ‘Stripe’ as an Example

  1. 1. ACCEPTING ONLINE PAYMENT FOR YOUR LIBRARY & ‘STRIPE’ AS AN EXAMPLE Code4Lib DC Unconference, Aug. 11-12, 2014. Bohyun Kim Associate Director for Library Applications and Knowledge Systems University of Maryland, Baltimore Health Sciences and Human Services Library Twitter: @bohyunkim Website:
  2. 2. Elements of Online Payment  ACH (Automated Clearing House) payments: Electronic credit and debit transfers. Most payment solutions use ACH to send money (minus fees) to their customers.  Merchant Account: A bank account that allows a customer to receive payments through credit or debit cards. Merchant providers are required to obey regulations established by card associations. Many processors act as both the merchant account as well as the payment gateway.  Payment Gateway: The middleman between the merchant and their sponsoring bank. It allows merchants to securely pass credit card information between the customer and the merchant and also between merchant and the payment processor.  Payment Processor: A company that a merchant uses to handle credit card transactions. Payment processors implement anti-fraud measures to ensure that both the front-facing customer and the merchant are protected.  PCI (the Payment Card Industry) Compliance: A merchant or payment gateway must set up their payment environment in a way that meets the Payment Card Industry Data Security Standard (PCI DSS).  Source:
  3. 3. How Online Payment Works Different payment gateways, merchant accounts, and bank accounts are setup to work together (or not). Your bank may also be able to act as the merchant account. Source: 2012/10/10/introduction-to- stripe/
  4. 4. Online Payment Systems   PayPal  Google Checkout  Amazon Payments  Stripe  WePay  Dwolla  Braintree  Samurai Source: systems/
  5. 5. Stripe Stripe acts as both the payment gateway and the merchant account. Your website communicates the customer and order information to Stripe, Stripe clears the payment information with the associated credit card company, and Stripe puts the money in your bank account. Source: http://www.larryullman.c om/2012/10/10/introducti
  6. 6. API Keys for Testing
  7. 7. Resources  Card Numbers for Testing  Code Examples  Docs
  8. 8. Starting Point  Borrowed example from Stripe-Payment-Form
  9. 9. When the Payment Succeeds,
  10. 10. Modify and Enhance  Add Patron & Payment Details.  Allow custom amount for payment.  Change the currency to USD.  Configure the validation for new fields. (Bootstrapvalidator jQuery Plugin)  Hide the payment form once the charge goes through.  Other examples:
  11. 11. Process  You create a form on your website that accepts the payment details.  You include a Stripe JavaScript library on the page.  You write a JavaScript function that watches for the form submission (i.e., you create an event handler for the form’s submission).  When the form is submitted, the user’s payment details are securely sent to Stripe via Ajax.  Stripe will confirm that the payment information is valid and return a token that uniquely identifies that payment information.  The JavaScript function that handles the Ajax response stores the token in a hidden form element and submits the form.  The server-side script (aka, the PHP code) that handles the form’s submission uses the token to actually process the payment.  So the customer never leaves your site but the payment information never hits your server: the best of both worlds. (This is the process when all works well; payment verification errors introduce new processes.) Source: payments-with-stripe/
  12. 12. JS/jQuery
  13. 13. PHP
  14. 14. Modified Form
  15. 15. Testing
  16. 16. Dashboard
  17. 17. Logs
  18. 18. Token Request
  19. 19. Charge Request
  20. 20. Failed Charge
  21. 21. Charge Response - Declined
  22. 22. Error Codes
  23. 23. More to be Done  Send the confirmation e-mail upon the payment success.  … More.
  24. 24. Questions? Photo credit: Flickr Nina`H