2017-07-17 Meeting notes

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes

SJSU PayPal model

https://github.com/CSU-ULMS/Primo-PayFineFee-with-Paypal

Jessie Cai, Christina Mune
  • Must attach a US taxpayer to the account, not an institution ID - you must identify who will be the taxpayer attached to the accountDid you talk to somebody on campus about already existing institutional accounts - it was between PayPal and Square - the site was not as customizable - couldn’t have logo.  Campus ITS does not have a pre-existing PayPal account we could use.  As long as the service had transactions hosted on their server.  In order to have Square API - had to self-host the whole transaction here


    PayPal is very easy to integrate with 


    Could not retrieve student’s ID from paypal - student has to enter their primo ID, and check the balance


    Callback script - pdt.php listens for PayPal transactions - PayPal sends the custom variable (student ID) and the payment total amount - update the paid amount.


    PayPal has two protocols -PDT - Payment data transaction - if you want instant, you need PDT;

    IPN - has a time delay

    One drawback using PDT only sent once, if there’s a network problem - the transaction notification can be lost.  It is recorded in the PayPal account history, if a transaction was lost.  User also receives a payment notification, as does a generic library account email.


    PayPal payment screen  populates amount owed; amount cannot be changed

    Users cannot pay partial amounts; there is an option when setting up the PayPal Business Account - can set up an option to enable the user to specify the amount


    Standard Business Account is free — Premier has additional customizations ($30/month)


    On the form you created - was it PCI scanned?  No user information, the student ID is the only thing being entered.  ID alone did not represent a security concern


    Cannot pull back the username from student PCI, but will still need intermediary script between Primo to get the payment info (would normally be collected through PayPal button)


    Wherever you host the script - would have to set up the Shib service provider their - would be invoked and could grab the user ID from that.  It might be easier to look for a solution on the Primo side - to use the Angular.js to grab the username.  We could construct a link from Primo’s session info, and pass in the user ID


    Would need to learn a little more about the IT/security end / PCI compliance


    Next steps:  Take the San Jose Solution - make it anonymous, strip out the branding, etc.  Organize in a way that it can be done with multiple campuses - move common files into a /lib file and create separate folders for campuses using the same library.  @lauren to work with @jessie


    Experiment with the angular piece to experiment with pulling out the username - Jessie - interested in the Angular.js solution - Ian’s been looking at this a bit - Dave to work with Jessie and Ian


    Understand PCI compliance - @Eva - has a case - they were never able to fix all of the PCI issues 00448437


    Dave will interface re: specific questions for CO financial folks, who set up the systemwide PayPal stuff to enable CSUOnline system

 

 Other Fine/Fee payment considerations, additional features needed for other CSUs?

  • Some campus financial people may not "like" PayPal / prefer CashNet, but still may not be willing to pay for CashNet eMarket
  • Other campuses may prefer Bursar model
  • CO hosting needed/desired?
  

Action items

  •