Page 1 of 1

OCCCUU Payment system features

Posted: Mon Jun 18, 2012 4:24 am
by TestUser
We students from the University of Applied Sciences Vorarlberg wanted to use the Cyclos server to provide payment services for the OCCCU project (http://occcu.com/index.php). OCCCU is a basic income experiment using an alternative currency. We tried to implement the following extensions, but we did not succeed.

Tried Extensions:

1.) Integrate Payswarm
Goal:
- Extend the server to accept transactions in the Payswarm protocol
Problems:
- The client needs an own certificate for authentication.
- The certificates are expensive.
- The network connection must be encrypted.
- The protocol is not a standard yet.

2.) Pay by barcodes
Goal:
- Encode transaction information in a barcode.
- Scan the barcode with a smartphone and perform the transaction with the encoded information using the existing web service.
Deliverables:
- Java web application to generate the barcodes.
Problems:
- The libraries for the web service proxy are very big for a mobile device (~7MB).
- There is not a proxy for Objective C.
- But the iOS has a big market share.

3.) Integrate a pay button
Goal:
- Provide a code snippet for websites to start a transaction with the WebPOS interface.
- The transaction information is provided in a hidden form.
- Clicking on the button redirects to the WebPOS website and the transaction information is already inside the form.
Problems:
- The WebPOS needs a login at the beginning.
- Login and hold the session.
- A successful login does not redirect to the initial target.
- The WebPOS url does not provide parameters for the transaction information.
- PHP may not be available on a web server to use the PHP classes.
- Get a ticket via PHP.

4.) Interactive Payment form
Goal:
- Provide a code snippet for websites to start a transaction with the WebPOS interface.
- The transaction information is provided in a hidden form.
- Clicking on the button redirects to the WebPOS website and the transaction information is already inside the form.
- Provide additional inputs to change the transaction information before clicking the button.

Problems:
- The WebPOS needs a login at the beginning.
- Login and hold the session.
- A successful login does not redirect to the initial target.
- The WebPOS url does not provide parameters for the transaction information.
- PHP may not be available on a web server to use the PHP classes.
- Get a ticket via PHP.
- The ticket cannot be changed.