search

RajatShukla / getpaid

Automatically exported from code.google.com/p/getpaid
0 stars 0 forks source link

implement possibility to do a refund, an offline payment, and a recurring charge #158

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Right now, the only process available is an Authorization followed by a
Mark for Capture

What is the expected output? What do you see instead?
We would need to give the merchant the possibility:
 * to allow authorization (maybe this one should be by default)
 * to allow capture
 * to allow offline payment
 * to do the refund by himself

I have seen that in Authorize net the code is ready for the refund. Also, I
can implement it for the Paymentech part. For the offline payment, we will
have to modify a bit the checkout process to allow the user to select this
option.

Original issue reported on code.google.com by lucielej...@gmail.com on 15 Dec 2007 at 4:55

GoogleCodeExporter commented 9 years ago

Original comment by lucielej...@gmail.com on 15 Dec 2007 at 4:55

GoogleCodeExporter commented 9 years ago 
Growing the issue title to a bit more of a feature request. 

Would like to see that we have a standard way of building in recurring payment
options also, and this will need to be taken in to account for pay processor
implementations. 

For example, we could have a new "delivery" method, which could be "make 
recurring
billable" or something...and it would make it buyable, but also make the 
purchase
recurring (and interface with the pay processor's info for setting daily, 
weekly,
monthly, annually...).

Original comment by cjj.ifpe...@gmail.com on 13 Feb 2008 at 4:27

GoogleCodeExporter commented 9 years ago

Original comment by cjj.ifpe...@gmail.com on 22 Aug 2008 at 6:22