Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0004617 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [Java Client POS] (No Category) | minor | always | 2008-08-13 06:02 | 2008-10-07 11:45 | ||||||
| Reporter | thelurker | View Status | public | ||||||||
| Assigned To | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | 2.10 MP1 | SCM revision | |||||||||
| Regression date | |||||||||||
| Regression introduced by commit | |||||||||||
| Regression level | |||||||||||
| Review Assigned To | |||||||||||
| Regression introduced in release | |||||||||||
| Summary | 0004617: Need plug-able architecture for payment gateway code | ||||||||||
| Description | Adding 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 Reproduce | API is current insufficient. | ||||||||||
| Proposed Solution | This 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. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
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) |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |