Difference between revisions of "Allow Payment"

From TimeSnapper
m
 
Line 7: Line 7:
 
* for a single product -- it's only a few lines more complicated than that
 
* for a single product -- it's only a few lines more complicated than that
  
 +
Click on the payment button (or buttons) takes the customer to the gatway's site, where they enter their credit card and other detaisl as needed. You never see these details (and you never want to !).
 +
 +
Going near credit card numbers is a responsibility you do not want.
 +
 +
 +
Once the payment is made, there is a ping to a website you specify, and also, the customer is redirected to your page.
 +
 +
You'll email the customer with the license info, and also show the license info on screen (in case they don't get the email).
  
  
 
This is step 11 of [[25 Steps to Build Your Own Micro ISV]]
 
This is step 11 of [[25 Steps to Build Your Own Micro ISV]]
 
[[Category:MicroISV]]
 
[[Category:MicroISV]]

Latest revision as of 17:06, 15 November 2009

This is step 11 of 25 Steps to Build Your Own Micro ISV


  • don't build a shopping cart
  • don't read all of the developer documentation -- most of it is for more complicated situations
  • start by working out how to implement a donation button
  • for a single product -- it's only a few lines more complicated than that

Click on the payment button (or buttons) takes the customer to the gatway's site, where they enter their credit card and other detaisl as needed. You never see these details (and you never want to !).

Going near credit card numbers is a responsibility you do not want.


Once the payment is made, there is a ping to a website you specify, and also, the customer is redirected to your page.

You'll email the customer with the license info, and also show the license info on screen (in case they don't get the email).


This is step 11 of 25 Steps to Build Your Own Micro ISV