search

kapilt / getpaid

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

Need to document pay processor interface requirment re this issue #118

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Choose the month and date from drop-downs during checkout process
2. Click 'Make Payment' button
3. Receive the 'Credit card expiration date is invalid.' status message.

What is the expected output? What do you see instead?
I would expect to see the 'order processed' message, but instead see
'Credit card expiration date is invalid.'

I believe that the expected year format is simply YY and instead we are
populating it with CCYY, so the payment processor returns an error.

No orders can be completed until this is fixed.  I believe we either need
to populate the selection's stored values with YY (and either display CCYY
or YY), or we need to strip the CC from CCYY when posting the date to the
processor.

Original issue reported on code.google.com by ctxl...@gmail.com on 24 Sep 2007 at 6:32

GoogleCodeExporter commented 8 years ago

Original comment by cjj.ifpe...@gmail.com on 24 Sep 2007 at 8:40

GoogleCodeExporter commented 8 years ago 
The Authorize.net API shows that MMYYYY and MM-YYYY should be an allowed 
format, but
the widget is formatting in YYYY-MM format.

I tried swapping the formatting around, so that it is MM-YYYY, but it didn't 
work for me.

I noticed that in the zc/authorizenet/processing.py uses the MMYY format and 
this is
what worked previously when exp_date was using a simple TextLine widget.

Perhaps the API is outdated and doesn't allow for the date to be in YYYY-MM 
format?

The exp_date API is on page 16 of the API here: 
http://www.authorize.net/support/AIM_guide.pdf

Original comment by ctxl...@gmail.com on 25 Sep 2007 at 4:22

GoogleCodeExporter commented 8 years ago 
Authorize.net processor modified for use the format MMYY as requested. I 
couldn't
tested it because as I applied for a testing account today, I don't have it yet.

Can you please check if works for you now?

Any other payment processor code must explicitly choose it's date format

Original comment by javimans...@gmail.com on 25 Sep 2007 at 9:05

GoogleCodeExporter commented 8 years ago 
A little more detail on what each payment processor code must do about choosing 
date
format:

def authorize(self, order, payment):
    #... things
    exp_date = payment.cc_expiration.strftime('%m%y')
    # ... more things

So, as you can see, payment.cc_expiration is a DateTime object from which you 
can ask
the string format needed.

Original comment by javimans...@gmail.com on 8 Oct 2007 at 4:49

GoogleCodeExporter commented 8 years ago 
This is fixed in the authnet case. We should convert the above details for pay
processors to documentation about how to integrate them, and that should 
conclude the
issues.

Original comment by cjj.ifpe...@gmail.com on 15 Oct 2007 at 11:22

GoogleCodeExporter commented 8 years ago

Original comment by cjj.ifpe...@gmail.com on 24 Oct 2007 at 10:10

GoogleCodeExporter commented 8 years ago 
moving this from m1 since the release doesn't depend on it
hopefully with 3 pay processors (ogone, authnet, paymentech) it will be clear 
enough :)
it would still be great to have some documentation about this when possible

Original comment by cjj.ifpe...@gmail.com on 27 Nov 2007 at 2:03

GoogleCodeExporter commented 8 years ago

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