Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Java Client POS] (No Category)minoralways2008-08-13 06:022008-10-07 11:45
ReporterthelurkerView Statuspublic 
Assigned To 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.10 MP1SCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Regression introduced in release

0004617: Need plug-able architecture for payment gateway code

DescriptionAdding new payment gateway implementations currently necessitates the editing of JPanelConfigPayment and JPaymentlMagCard to add the gateway as an option in the select list and also add any addition configuration options or mandatory data entry during credit card processing.

Since each gateway may have a different sent of options there should be a way to install or dynamically load a .jar containing all of the code and resources for a gateway implementation and also code to configure the gateway. In addition there should be an option to provide the payment panel as well since additional requirements such as Billing Telephone may be required before a credit card payment can be submitted to a gateway.

This is a nice to have feature so that payment gateway implementations are more independent and won't conflict.

Steps To ReproduceAPI is current insufficient.
Proposed SolutionThis is just a sketch...
1. Ability to package payment gateway code and resources (messages) in separate stand alone jar.
2. Make pos system dynamically load all manifests from lib/gateways/*.jar to dynamically build the gateway selection list.
3. When a payment gateway is chosen a button entitled "Configure" allows user to set options for the gateway such as IP, Email, Merchant ID, Merchant Password, and any other options such as Certify etc.
These options are persisted for later retrieval.
4. For whatever payment gateway is chosen, the payment gateway jar is dynamically loaded and the derived instance of JPaymentMagCard from the jar (identified in the manifest or dynamically) is instantiated and added as one of the payment options.

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 00053582.30 closedadrianromero Payments gateways 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2008-08-13 06:02 thelurker New Issue
2008-08-13 06:02 thelurker sf_bug_id 0 => 2048996
2008-10-07 11:45 adrianromero Status new => acknowledged
2008-10-07 11:45 adrianromero Relationship added related to 0005358
2012-11-07 09:40 priyam Category 01 - General => (No Category)

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker