The Authorize.Net Developer Blog - Page 2

Mobile payments are all the talk these days, but what security hurdles need to be overcome?

The payment form we created in the first five parts of this series is very good. But it could be better. Part 6 begins a new chapter in this series where we improve upon our payment to make it more usable, secure, and maintainable. We begin by preventing users from making duplicate form submissions by using the POST/REDIRECT/GET design pattern. 

Attachments:

payment-form.zip ‏6 KB

In Part 5 of our series we are past receiving and validating data and get to the nitty gritty of processing the payment using the  PHP SDK.

Ever wondered about PCI-DSS or PA-DSS and thought “why me” or “why bother”? Read on for a little insight.

In part 4 of our series we take the errors we captured in part 3 and display them to our users in a friendly and intuitive way.

In the world of development, it’s easy to get confused by the differences between these two.  It is not uncommon to see some companies provide you an SDK and call it an API.  Read on for a brief definition of the terms as viewed by Authorize.Net.

In part 3 of our series on handling online payments we take the data we sanitized in Part 2 and validate it to make sure it is values we expect and can work with.

In retail merchant software (like our Credit Card Terminal app), exposing the AIM void and credit actions directly to the user is a poor choice. I'll talk about why and propose an alternative "unified" refund action, including sample code.

Relay Response is a useful tool for customizing your own receipt page and handling transaction information. Here we’ll talk about some basic troubleshooting tips.

In part 2 of our series on handling online payments we take the form we created in part 1 and show how to properly receive and sanitize the information. Examples of how to do this with PHP is included.

If you’ve ever been confused about the differences between test accounts and live accounts, or test mode and live mode, then check out this brief explanation of what each is and what each does.

Think you're payment form is secure and follows best practices? This series will highlight the common pitfalls overlooked by many developers and demonstrate best practices to make sure your users experience a quick, friendly, and safe checkout. Part 1 will get us started by determining what information we will want to capture and start to build the HTML form we will use to capture that information.

Security is important for any website, doubly so for ecommerce websites as accepting payments makes any website a tempting target for hackers. In this blog post we show some simple HTTP headers your website can use to increase security that are quick and easy to implement.

Handling dollar amounts isn't as simple as adding two numbers together. PHP, and other programming languages, have limitations to how precise they can be. This blog post will show you how to do precise money calculations using PHP's BC Math extension.

Ever wondered whether you should use CIM or ARB for recurring transactions? You're not alone. Check out the differences between the two here.

When you create a profile on CIM, or even ARB, you eventually need to have the customer update their credit card because it is about to expire. But how to you know when the card is about to expire without storing the expiration date and having PCI compliance issues? We show you how with a short PHP snippet.

The last of a three part series on how to validate credit card information. Examples are provided using PHP.

There have been a lot of changes to .NET over the last few years and I'm pleased as punch to see the new Authorize.Net SDK take advantage of these changes.

The second of a three part series on how to validate credit card information. Examples are provided using PHP.

The first of a three part series on how to validate credit card information. Examples are provided using PHP.

Authorize.Net recently launched the Direct Post Method (DPM) which makes it faster than ever to take full control of the checkout process.

Get payments up and running quickly with the new PHP SDK from Authorize.Net.

Things are different around here.

In the coming weeks, we’ll begin our foray into the blogosphere, but before we do, I’m curious. What kinds of topics would you all like to see discussed?