have credit card payment act depending on credit card org unit settings
Bug #1376843 reported by
Rogan Hamby
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Wishlist.
When entering a credit card payment do not display the "Process Payment Through Evergreen" screen if the credit card settings aren't set for that org unit.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
tags: | added: billing circulation wishlist |
tags: |
added: circ-billing removed: billing wishlist |
To post a comment you must log in.
I'll see your wishlist request and raise you another wishlist request.
Ideally, what I would like to see here is, rather than a True / False option for the Enable Credit Card Payments setting, is three options: opac, client, or both.
If set to OPAC, the option to submit a credit card payment is only available via the public catalog.
If set to staff, the "process payment through Evergreen" option in the credit card payment screen does not appear, but credit card payment is still available with the option to process it through an external source.
If set to both, the option is available in both places.
As of now, I believe you can allow credit card payments solely via the staff client, simply by adding the processing information, and then you can make it available through the catalog by setting the Enable Credit Card Payments setting to True.
However, you don't have the ability to make it available in the catalog, but not in the client.
We have libraries that would like to allow patrons to pay via credit card online, but don't want staff handling credit cards over the desk. Allowing distinct options for where libraries want to take credit card payments would add a nice flexibility to the system.