Cybersource
Cybersource Services.
http://www.cybersource.com/developers/learn/cybersource_services/
Can implement each independently.
Payment and Card Authorization
http://www.cybersource.com/developers/learn/getting_started/how_payment_processing_works/
There are a number of ways to integrate but I prefer use Simple Order API or Soap api. They support multiple languages php, Java, Perl, C# etc. You can pass data as name value pairs or xml.
I'd recommend Soap API for php especially with Soap built into php now. I defined a simple php class to hold params to be passed and then passed a new instance of that class to the Soap call.
Cybersource provide a class ExtendedClient to facilitate the Soap call.
The api will return a object you can assign to a class.
Cybersource also provide useful sample code and test clients. Very thorough.
Address Verification
This is very like Card authorization explained above and I'd do the same approach if implementing (Soap with php).
For address verification tou get a response object back and:
if all is ok you need to check if some fields were modified by Cybersource (called "standardizing") and save them
if it fails (!isValid) then you get a reasonCode indicating the issue.
Cybersource allow clients to do "device fingerprinting" by including some tags and a js file on your Submit Order page html which allow Cybersource to uniquely identify a client. Feeds info to Decision Manager.
http://www.cybersource.com/developers/learn/cybersource_services/
Can implement each independently.
Payment and Card Authorization
http://www.cybersource.com/developers/learn/getting_started/how_payment_processing_works/
There are a number of ways to integrate but I prefer use Simple Order API or Soap api. They support multiple languages php, Java, Perl, C# etc. You can pass data as name value pairs or xml.
I'd recommend Soap API for php especially with Soap built into php now. I defined a simple php class to hold params to be passed and then passed a new instance of that class to the Soap call.
Cybersource provide a class ExtendedClient to facilitate the Soap call.
The api will return a object you can assign to a class.
Cybersource also provide useful sample code and test clients. Very thorough.
Address Verification
This is very like Card authorization explained above and I'd do the same approach if implementing (Soap with php).
For address verification tou get a response object back and:
if all is ok you need to check if some fields were modified by Cybersource (called "standardizing") and save them
if it fails (!isValid) then you get a reasonCode indicating the issue.
Decision manager
Decision Manager is a management tool developed by Cybersource for Fraud protection purposes that gives flexibility to control business practices and policies in real time and to interpret the risk and information codes based on custom, user-defined, business rules. With Decision Manager, you can accurately identify and review potentially risky transactions while minimizing the rejection of valid orders.
Cybersource allow clients to do "device fingerprinting" by including some tags and a js file on your Submit Order page html which allow Cybersource to uniquely identify a client. Feeds info to Decision Manager.
Comments
Post a Comment