Hey, I'm still around. Yahoo seems to delay delivery of my emails, may be I should move to gmail...
I'm aware of 2 companies that are building such a solution and 1 company that has already built it, and a group of developers from Coast who are planning on building it. I think it will be important to meet them and see what they have (in terms of the requirements I've listed below), what the revenue share structure is and any other important info.
Below are my contributions:
Problem definition:
Refer to first email on this thread:
Requirements:
1. Intergration in as many platforms as possible, but most important platforms for a start: Web browser, Mobile, PC/Mac Apps.
2. Open API for developers.
3. Secure: Secure trasmission of data, security of the client data, security of the server infrastructure (hardware and software).
4. Simple, predictable steps for client to make transactions. Simple registration.
5. Common look and feel of the payment UI across platforms in order to build confidence about the system in clients. E.g. a common logo.
6. Registered entity that takes responsibility of the system, customer support, ...
7. System should handle refunds or transaction rollbacks.
8. System should handle client sessions robustly. If client session is terminated, store data, and remind client when client does the next transaction. This seems simple at first but might not be so e.g: If client was subsribing for a service on mobile then battery died or something happened that caused client to go offline, then if client logged into web to use the payment system for a different product then client should be aware of the terminated mobile transaction.
9. Audit system to, among other things, keep track of un-used Serial numbers and the vendor with the serial numbers.
10. Regular back-up system and a sound disaster recovery plan.
O_O --- On Thu, 9/17/09, Solomon Mburu <solo.mburu@gmail.com> wrote:
|