Re: Payflow Pro help is here

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 42891
interpreted = N
texte = Hi Dale, thanks for the post... I do think there should be a step-by-step html page somewhere for this. (if I ever succeded in OS9, I would definately post something)I still haven't been able to get past a communications error. (-31) Cannot find local cert... I thought my template was just about as simplistic as you can get with everything being hard coded in the .class file. Just can't seem to get a clean connection... I'm courious though about your comment about that specific test CC number. I believe I've been using a different one. Anyway, We are using the BK method also.. I asked verisign if these CC numbers would work on those type of tests and they responded yes, they should.Anyway, your info will come in handy (once I get to the WebCat templates.) (I'm about ready to give up and try the Signio templates.)occassionally I get another error: JSSE jar files not found in CLASSPATH Anyway, thats where I'm at right now. I'll try your test CC num next monday.OS9 / WebDNA 4.5P.S. I believe Dennis Bonsall was having issues also.. Dennis, any new thoughts?DonovanDale LaFountain wrote:> Hi Donovan (and list), > > It looks like Donovan and I are the only two people working on > Payflow Pro at the moment, so maybe we can help each other. If > anyone else wants to jump in and help, please feel free... > > I spent most of today poring over the various WebMerchant templates > and includes, as well as the Payflow and WebMerchant docs. This is > what I discovered along the way: > > In PayFlow_Pro_Verisign.inc, there is a lookup for the > WebMerchantPrefs.db value PayFlowProClassPath, which is passed to the > java object later in the include. This value didn't exist in my > WebMerchant Prefs nor is it available in the web admin, so I added it > manually: > > PayFlowProClassPath /usr/local/verisign/Verisign.jar > > I also needed to add a couple things to account for the Verisign > partner id requirement to the Payflow include and webmerchantprefs.db: > > To Payflow_Pro_Verisign.inc: > [text]partner=[lookup > db=WebMerchantPrefs.db&lookInField=preference&value=PayFlow_Pro_Partner&returnField=value][/text] > [Text]po16=[partner][/Text] > > To WebMerchantPrefs.db: > PayFlow_Pro_Partner verisign (or whatever was assigned to you; > ours is wfb for Wells Fargo) > > I was able to run the javatest.pl script (on OSX here) and receive a > test approval from Verisign, and I have since made a few test > tranactions using webcat carts and ProcessOrders.tpl. I'm currently > making a list of all the things we will need to tweak to transition > from Cybercash on OS9/Webcat3.07 to Payflow Pro on OSX/webcat4.5, > like AVS response being two letters long instead of one, sending the > Payflow RefNum as the AccountNum on the second step of Book/Ship, > etc... > > I also removed the webcat comments around the > Orders/ShoppingCarts/Problems/Completed display code in > AdminPrefs.tpl that Jay commented out sometime around 5/10/2000 when > the OSX version of webcat didn't support webmerchant. I seem to > remember being the one that complained about those misleading entries > in the prefs right after buying my first wc license for OSX... It > seems fitting that I should be the one to announce their removal over > 2 years later... The circle is now complete! :) > > I haven't figured out what the rules are (or found them in the docs) > to test various transaction responses, i.e the only card number I > have been able to get an Approval for so far (in test mode) is > 4222222222222. I have tried other test card numbers as well as a > couple valid cards, an they all return declined... > > I hope this helps Donovan and anyone else who digs this up in the > archive if/when they want to use Payflow. If SMSI is listening, they > should add this stuff to their templates for the next release because > it's all required to get the current version of Payflow Pro to > function properly. > > I will also try to write up a more complete howto for the list once I > get everything running smoothly. > > Later, > > -Dale > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Payflow Pro help is here (Donovan 2002)
  2. Re: Payflow Pro help is here (Dale LaFountain 2002)
  3. Re: Payflow Pro help is here (NovaDerm Skincare Science 2002)
  4. Re: Payflow Pro help is here (Donovan Brooke 2002)
  5. Payflow Pro help is here (Dale LaFountain 2002)
Hi Dale, thanks for the post... I do think there should be a step-by-step html page somewhere for this. (if I ever succeded in OS9, I would definately post something)I still haven't been able to get past a communications error. (-31) Cannot find local cert... I thought my template was just about as simplistic as you can get with everything being hard coded in the .class file. Just can't seem to get a clean connection... I'm courious though about your comment about that specific test CC number. I believe I've been using a different one. Anyway, We are using the BK method also.. I asked verisign if these CC numbers would work on those type of tests and they responded yes, they should.Anyway, your info will come in handy (once I get to the WebCat templates.) (I'm about ready to give up and try the Signio templates.)occassionally I get another error: JSSE jar files not found in CLASSPATH Anyway, thats where I'm at right now. I'll try your test CC num next monday.OS9 / WebDNA 4.5P.S. I believe Dennis Bonsall was having issues also.. Dennis, any new thoughts?DonovanDale LaFountain wrote:> Hi Donovan (and list), > > It looks like Donovan and I are the only two people working on > Payflow Pro at the moment, so maybe we can help each other. If > anyone else wants to jump in and help, please feel free... > > I spent most of today poring over the various WebMerchant templates > and includes, as well as the Payflow and WebMerchant docs. This is > what I discovered along the way: > > In PayFlow_Pro_Verisign.inc, there is a lookup for the > WebMerchantPrefs.db value PayFlowProClassPath, which is passed to the > java object later in the include. This value didn't exist in my > WebMerchant Prefs nor is it available in the web admin, so I added it > manually: > > PayFlowProClassPath /usr/local/verisign/Verisign.jar > > I also needed to add a couple things to account for the Verisign > partner id requirement to the Payflow include and webmerchantprefs.db: > > To Payflow_Pro_Verisign.inc: > [text]partner=[lookup > db=WebMerchantPrefs.db&lookInField=preference&value=PayFlow_Pro_Partner&returnField=value][/text] > [text]po16=[partner][/Text] > > To WebMerchantPrefs.db: > PayFlow_Pro_Partner verisign (or whatever was assigned to you; > ours is wfb for Wells Fargo) > > I was able to run the javatest.pl script (on OSX here) and receive a > test approval from Verisign, and I have since made a few test > tranactions using webcat carts and ProcessOrders.tpl. I'm currently > making a list of all the things we will need to tweak to transition > from Cybercash on OS9/Webcat3.07 to Payflow Pro on OSX/webcat4.5, > like AVS response being two letters long instead of one, sending the > Payflow RefNum as the AccountNum on the second step of Book/Ship, > etc... > > I also removed the webcat comments around the > Orders/ShoppingCarts/Problems/Completed display code in > AdminPrefs.tpl that Jay commented out sometime around 5/10/2000 when > the OSX version of webcat didn't support webmerchant. I seem to > remember being the one that complained about those misleading entries > in the prefs right after buying my first wc license for OSX... It > seems fitting that I should be the one to announce their removal over > 2 years later... The circle is now complete! :) > > I haven't figured out what the rules are (or found them in the docs) > to test various transaction responses, i.e the only card number I > have been able to get an Approval for so far (in test mode) is > 4222222222222. I have tried other test card numbers as well as a > couple valid cards, an they all return declined... > > I hope this helps Donovan and anyone else who digs this up in the > archive if/when they want to use Payflow. If SMSI is listening, they > should add this stuff to their templates for the next release because > it's all required to get the current version of Payflow Pro to > function properly. > > I will also try to write up a more complete howto for the list once I > get everything running smoothly. > > Later, > > -Dale > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

webcat2b12 CGI -- Date comparisons (1997) OFF TOPIC: Sendmail problem (2003) need to add a sku field to an existing db (2005) Saving [referrer] for later use (1997) TCPConnect strange behaviour (2004) Additional Subtotals (1999) Problems with [Search] param - Mac Plugin b15 (1997) Configuring E-mail (1997) RE: [WebDNA] TRIM (2008) Numbers and Numbers and Me (1999) Item options w/ price adjustment (1997) How is it done? (1998) Progress !! WAS: Trouble with formula.db (1997) Deleting duplicates from a db (2000) Online reference (1997) auto enter dates (1998) WebCat for Unix?? (1997) Exclamation point (1997) 300% usage - Clint (2007) [WebDNA] test (2008)