Re: [WebDNA] Accepting Payments on Site
This WebDNA talk-list message is from 2013
It keeps the original formatting.
numero = 110325
interpreted = N
texte = Thanks Mike, I'd be really interested in what this notified page looks like in WebDNA since the only documentation I'm seeing is for PHP, ASP and others. On 4/11/13 11:23 PM, "Michael Davis"
wrote: >Eddie, > You're almost there. The next step is to enable IPN on your PayPal >account (it's a setting in your PayPal acct. panel). IPN allows you to >create a page on your site that PayPal will "notify" when the payment has >been processed. This notification contains the original payment's >invoice identifier, so if you have an invoice number that also identifies >the customer via a lookup, you're golden. I have a pile of code I can >give you that works well with IPN if you need more help. > > >Mike > >On Apr 11, 2013, at 9:02 PM, Eddie Z wrote: > >> Thanks for the feedback everyone. Considering we only accept payments >>for >> several months a year, I guess it doesn't make a lot of sense to leave >> Paypal, but I need to figure out a better process. >> >> The way I have it now: >> A team fills out a form and I write all of their info to a db and send >> them to a payment page that figures out how much they owe + has a link >>to >> make the payment on Paypal. They are sent to Paypal with a variable that >> gets passed through the process. Once the payment is made people are >>asked >> to click on a button to return to my site, which also passes the >>variable >> back and lets me know the transaction is completed. Many people skip >>this >> step so I'm stuck trying to compare my Paypal payments to teams in my >> database. >> >> I'm interested in Terry's statement: (they do a silent return just like >> authorize.net). I'm about to Google it, but if you have details I'd love >> to hear about it. It may solve some issues for me. >> >> >> Eddie >> >> On 4/11/13 7:44 PM, "Terry Wilson" wrote: >> >>> I concur with Stuart, but I'm going to also check out this site. I'll >>> definitely read the fine print on it. But really, for a one-off, >>> yeah, just stick with PayPal. I know what you mean about people >>> bailing, but at least you know when it happens, and can write code to >>> only complete the transaction when PayPal gives you the high sign >>> (they do a silent return just like authorize.net). It's very easy to >>> implement a paypal form and a page to receive their confirmation. >>> >>> I use this on Whoscoming.com and if someone bails, their record is >>> intact, but it shows as payment pending. Collect payment at the door. >>> >>> I just finished my annual business overview and now more than ever >>> before, it's time to scrap my merchant account/authorize.net. I have >>> a Square account for random sales in person, PayPal for eBay and Etsy >>> (who now also runs cards under their own name), and a host of old >>> fashioned clients who pay by check. The misc charges imposed by my >>> processor just don't make sense for the small volume of cards I run. >>> Plus small people like me get slapped with a monthly compliance fee >>> now. There are many, many more choices available now than when I got >>> into this nearly 20 yrs ago. >>> >>> Terry >>> >>>> If I was setting up payment processing on a site now, I would look >>>> seriously at stripe.com >>>> >>>> It looks dead simple to implement (though I haven't done it). >>>> >>>> - Brian >>>> >>>> On Apr 11, 2013, at 4:12 PM, Stuart Tremain >>>> <webdna@idfk.com.au> wrote: >>>> >>>>> Eddie >>>>> >>>>> After many years of many different payment gateways and all the >>>>> fuss that goes on in the administrative area of merchant account, >>>>> fees etc, set up etc, for a one-off event that you are talking >>>>> about I would stick with the PayPal. >>>>> >>>>> Going through a payment gateway you will need a bank account with a >>>>> merchant facility, here in Australia that can cost $35 a month, the >>>>> list goes on. >>>>> >>>>> >>>>> On 12/04/2013, at 3:57 AM, Eddie Z >>>>> <eddie@thinksite.com> wrote: >>>>> >>>>>> I have built 100s of forms, but I have never linked one to a >>>>>> merchant account before, so I'm looking for some help/direction. >>>>>> >>>>>> I have a form built for a sporting event where teams register and >>>>>> then once their data is collected, it sends them to Paypal to make >>>>>> a payment. The main issue I have with this method is that often >>>>>> times teams will enter their info, get to the payment page at >>>>>> Paypal and then bail, which leaves me with an unfinished >>>>>> registration. I'm interested in skipping Paypal and doing it all >>>>>> right on my site, but I don't know what I all need to do. >>>>>> >>>>>> I know I will need a SSL certificate, and to use >>>>>> Authorize.net or someone similar to link to >>>>>> my merchant, but I don't know if there's anything special I need >>>>>> to do in the code. Ideally, I would need there to be some sort of >>>>>> confirmation from authorize.net that the >>>>>> payment was successful before allowing the registrant to have a >>>>>> completed transaction. >>>>>> >>>>>> I honestly don't know how much work is involved here. If it's a >>>>>> decent amount, I'd be willing to purchase someone's payment page >>>>>> code to save me time. >>>>>> >>>>>> Let me know if anyone could help or has advice, >>>>>> Thanks, >>>>>> Eddie >>>>>> --------------------------------------------------------- This >>>>>> message is sent to you because you are subscribed to the mailing >>>>>> list . To unsubscribe, E-mail to: archives: >>>>>> >>>>>>http://mail.webdna.us/list >>>>>>/t >>>>>> alk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>> >>>>> >>>>> --------------------------------------------------------- This >>>>> message is sent to you because you are subscribed to the mailing >>>>> list . To unsubscribe, E-mail to: archives: >>>>> >>>>>http://mail.webdna.us/list/ >>>>>ta >>>>> lk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>>> >>>> >>>> --------------------------------------------------------- This >>>> message is sent to you because you are subscribed to the mailing >>>> list . To unsubscribe, E-mail to: archives: >>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>> support@webdna.us >>> >>> >>> -- >>> Terry Wilson | terry@terryfic.com | http://terryfic.com >>> http://WhosComing.com - a simplified, affordable online reservation >>>system >>> iStockPhoto portfolio - >>> http://www.istockphoto.com/Terryfic3D?refnum=Terryfic3D >>> >>>------------------------------------------------------------------------ >>>-- >>> Attitude is the only difference between ordeal and adventure. >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >> >> >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > >--------------------------------------------------------- >This message is sent to you because you are subscribed to >the mailing list . >To unsubscribe, E-mail to: >archives: http://mail.webdna.us/list/talk@webdna.us >Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Thanks Mike, I'd be really interested in what this notified page looks like in WebDNA since the only documentation I'm seeing is for PHP, ASP and others. On 4/11/13 11:23 PM, "Michael Davis" wrote: >Eddie, > You're almost there. The next step is to enable IPN on your PayPal >account (it's a setting in your PayPal acct. panel). IPN allows you to >create a page on your site that PayPal will "notify" when the payment has >been processed. This notification contains the original payment's >invoice identifier, so if you have an invoice number that also identifies >the customer via a lookup, you're golden. I have a pile of code I can >give you that works well with IPN if you need more help. > > >Mike > >On Apr 11, 2013, at 9:02 PM, Eddie Z wrote: > >> Thanks for the feedback everyone. Considering we only accept payments >>for >> several months a year, I guess it doesn't make a lot of sense to leave >> Paypal, but I need to figure out a better process. >> >> The way I have it now: >> A team fills out a form and I write all of their info to a db and send >> them to a payment page that figures out how much they owe + has a link >>to >> make the payment on Paypal. They are sent to Paypal with a variable that >> gets passed through the process. Once the payment is made people are >>asked >> to click on a button to return to my site, which also passes the >>variable >> back and lets me know the transaction is completed. Many people skip >>this >> step so I'm stuck trying to compare my Paypal payments to teams in my >> database. >> >> I'm interested in Terry's statement: (they do a silent return just like >> authorize.net). I'm about to Google it, but if you have details I'd love >> to hear about it. It may solve some issues for me. >> >> >> Eddie >> >> On 4/11/13 7:44 PM, "Terry Wilson" wrote: >> >>> I concur with Stuart, but I'm going to also check out this site. I'll >>> definitely read the fine print on it. But really, for a one-off, >>> yeah, just stick with PayPal. I know what you mean about people >>> bailing, but at least you know when it happens, and can write code to >>> only complete the transaction when PayPal gives you the high sign >>> (they do a silent return just like authorize.net). It's very easy to >>> implement a paypal form and a page to receive their confirmation. >>> >>> I use this on Whoscoming.com and if someone bails, their record is >>> intact, but it shows as payment pending. Collect payment at the door. >>> >>> I just finished my annual business overview and now more than ever >>> before, it's time to scrap my merchant account/authorize.net. I have >>> a Square account for random sales in person, PayPal for eBay and Etsy >>> (who now also runs cards under their own name), and a host of old >>> fashioned clients who pay by check. The misc charges imposed by my >>> processor just don't make sense for the small volume of cards I run. >>> Plus small people like me get slapped with a monthly compliance fee >>> now. There are many, many more choices available now than when I got >>> into this nearly 20 yrs ago. >>> >>> Terry >>> >>>> If I was setting up payment processing on a site now, I would look >>>> seriously at stripe.com >>>> >>>> It looks dead simple to implement (though I haven't done it). >>>> >>>> - Brian >>>> >>>> On Apr 11, 2013, at 4:12 PM, Stuart Tremain >>>> <webdna@idfk.com.au> wrote: >>>> >>>>> Eddie >>>>> >>>>> After many years of many different payment gateways and all the >>>>> fuss that goes on in the administrative area of merchant account, >>>>> fees etc, set up etc, for a one-off event that you are talking >>>>> about I would stick with the PayPal. >>>>> >>>>> Going through a payment gateway you will need a bank account with a >>>>> merchant facility, here in Australia that can cost $35 a month, the >>>>> list goes on. >>>>> >>>>> >>>>> On 12/04/2013, at 3:57 AM, Eddie Z >>>>> <eddie@thinksite.com> wrote: >>>>> >>>>>> I have built 100s of forms, but I have never linked one to a >>>>>> merchant account before, so I'm looking for some help/direction. >>>>>> >>>>>> I have a form built for a sporting event where teams register and >>>>>> then once their data is collected, it sends them to Paypal to make >>>>>> a payment. The main issue I have with this method is that often >>>>>> times teams will enter their info, get to the payment page at >>>>>> Paypal and then bail, which leaves me with an unfinished >>>>>> registration. I'm interested in skipping Paypal and doing it all >>>>>> right on my site, but I don't know what I all need to do. >>>>>> >>>>>> I know I will need a SSL certificate, and to use >>>>>> Authorize.net or someone similar to link to >>>>>> my merchant, but I don't know if there's anything special I need >>>>>> to do in the code. Ideally, I would need there to be some sort of >>>>>> confirmation from authorize.net that the >>>>>> payment was successful before allowing the registrant to have a >>>>>> completed transaction. >>>>>> >>>>>> I honestly don't know how much work is involved here. If it's a >>>>>> decent amount, I'd be willing to purchase someone's payment page >>>>>> code to save me time. >>>>>> >>>>>> Let me know if anyone could help or has advice, >>>>>> Thanks, >>>>>> Eddie >>>>>> --------------------------------------------------------- This >>>>>> message is sent to you because you are subscribed to the mailing >>>>>> list . To unsubscribe, E-mail to: archives: >>>>>> >>>>>>http://mail.webdna.us/list >>>>>>/t >>>>>> alk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>> >>>>> >>>>> --------------------------------------------------------- This >>>>> message is sent to you because you are subscribed to the mailing >>>>> list . To unsubscribe, E-mail to: archives: >>>>> >>>>>http://mail.webdna.us/list/ >>>>>ta >>>>> lk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>>> >>>> >>>> --------------------------------------------------------- This >>>> message is sent to you because you are subscribed to the mailing >>>> list . To unsubscribe, E-mail to: archives: >>>> http://mail.webdna.us/list/talk@webdna.us Bug Reporting: >>>> support@webdna.us >>> >>> >>> -- >>> Terry Wilson | terry@terryfic.com | http://terryfic.com >>> http://WhosComing.com - a simplified, affordable online reservation >>>system >>> iStockPhoto portfolio - >>> http://www.istockphoto.com/Terryfic3D?refnum=Terryfic3D >>> >>>------------------------------------------------------------------------ >>>-- >>> Attitude is the only difference between ordeal and adventure. >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >> >> >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > >--------------------------------------------------------- >This message is sent to you because you are subscribed to >the mailing list . >To unsubscribe, E-mail to: >archives: http://mail.webdna.us/list/talk@webdna.us >Bug Reporting: support@webdna.us
Eddie Z
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:
Creating comums (1998)
OT: RAID Options (2004)
Using Plug-In while running 1.6.1 (1997)
Cross-platform file names? (2000)
appleshare/ip (1997)
font statistics (2003)
showif field is number (1997)
Search results templates (1996)
Sorting by highest number of matches unique to a field (2003)
FREE Web Server Monitor FREE (1997)
More on the email templates (1997)
sorted cart? (1998)
switching users (1998)
catagories (1997)
PCS Emailer's role ? (1997)
Correct Link for WebDNA Archives (2002)
Custom WebCat Prefs ... (1997)
Comments in db? (1997)
(no subject) (1997)
Changing Date Format in Field (1999)