On Tue, May 9, 2017 at 5:14 PM, Jason Stephenson wrote:
> Josh,
>
> Using PayPal is similar to Stripe, since the transaction is completed
> via PayPal and the CC data is not stored in Evergreen.
>
PayPal (including PayFlowPro) and Authorize.net both require CC data to
pass
Josh,
Using PayPal is similar to Stripe, since the transaction is completed
via PayPal and the CC data is not stored in Evergreen.
We disabled the staff client credit card interface by commenting out the
relevant menuitem in Open-ILS/xul/staff_client/server/patron/bill2.xul.
(IANM, that relevant
NOBLE uses Stripe in a similar way to GPLS.
Ron
On Tue, May 9, 2017 at 4:58 PM, Dawn Dale
wrote:
> Hi Josh,
>
> We are using Stripe and the credit card information does not reside on our
> servers. We are accepting payments via the TPAC currently. To allow
>
Hi Josh,
We are using Stripe and the credit card information does not reside on our
servers. We are accepting payments via the TPAC currently. To allow
payments in the library, our libraries are setting up kiosk and having the
patron go to their account and make the payment at the kiosk. This
Hello, we are currently using payflow pro, which I think means that our
evergreen server handles the CC data and puts it in PCI scope. From what I'm
reading, if we switched over to using Stripe, which uses a javascript library
client side to submit the payment, then it would take our server
Hi all,
I'm sending along a reminder that the Evergreen web team is scheduled to
meet tomorrow at 11 a.m. Pacific, 2 p.m. Eastern in the #evergreen IRC
channel on the freenode network.
A draft agenda is available at