On 18/07/2011, One Murithi <
o0murithi@gmail.com> wrote:
> On Sun, Jul 17, 2011 at 2:50 PM, Calvin Omari
> <
calvinebarongo@gmail.com>wrote:
>
>> Hi Skunks,
>>
>> Trust your weekend is cool,
>>
>> I am pondering on how to incorporate a credit card payment solutions to a
>> website I am working on and to enable payment online, anybody who has done
>> so (especially on php) please adivice on how to go about the following
>>
>
> Not sure about local solutions - I've heard I&M might provide the service.
>
> However, most payment gateway providers publish documentation on how to
> integrate:
>
http://developer.authorize.net/
> Or Paypal as Steve mentioned
>
>>
>> 1. Security levels e.g SSL (verisgn etc)
>>
>
> This is part of your application. Most API calls to payment gateway are done
> via secure connections
>
>
>> 2. How the transaction is done between banks or and the website
>>
>
> the short version (probably the general case)
> You need
> - a merchant account with a bank - this is where your money goes
> - an account with a payment gateway - payments are processed through the
> gateway
>
> - client provides payment information depending on type of card (names on
> card, card number, CVV code, address)
> - You push the card info plus your transaction information to the payment
> gateway (Usually secure http POST)
> - You process the response from the payment gateway - success or failure
> (might include the reason for the failure)
> - sometimes funds are not captured immediately from the client's bank
> - you might have to provide a callback service to which the
> payment gateway
> sends the result of capture (or failure)
> - proceed with fulfillment of what was paid for
>
> 3. Credit Card validation - how to verify whether the card is genuine
>>
>
> Assuming by genuine you mean, that which belongs to the owner, it might come
> down to simply deciding how confident you are that the client is who they
> say they are (existing clients will be less bothersome)
> : check items like location, address information, value of transaction e.t.c
>
>
>>
> 4. How to make the transaction semaless and secure
>>
>
> :: Seamless - you could store card and address info - so that check out
> simply involves confirmation
> - also allows you to execute scheduled charges (recurring services)
> :: protect sensitive information (card numbers, cvv e.t.c)
>
> This is a broad area - would suggest some research
>
>
> my two dururus
>
>
>> Regards
>>
>> --
>> Our greatest fear is not that we are inadequate,
>> but that we are powerful beyond measure.
>> It is our light, not our darkness, that frightens us.
>>
>> Calvin Omari Systems Software Developer
>>
http://www.facebook.com/barongo
>>
>> _______________________________________________
>> Skunkworks mailing list
>>
Skunkworks@lists.my.co.ke
>>
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
>> ------------
>> Skunkworks Rules
>>
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
>> ------------
>> Other services @
http://my.co.ke
>>
>
_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @
http://my.co.ke