The Authorize.Net Developer Blog

If you're looking for insights into the payments industry, check out Visa's blog, Visa Viewpoints.

You have registered your domain name, built your website and have added all the products or services that you'd like to sell. Now what?  Your next step is to get a merchant account and a gateway account so that you can accept online payments from your customers.

Tokenization is used in payment systems and payment integrations to replace sensitive credit card data in a business system so the system no longer has to be subject to PCI Compliance regulations.
 

• How does Tokenization work?
• Who can use Tokenization?
• How does Tokenization compare to encryption?
• How does CRE Secure work with Authorize.Net to provide complete tokenization?

Love the Authorize.Net Developer Center? Then you'll love this one, too.

Find out more about our weekly Affiliate trainings.

If it isn't broke, don't fix it. Unless it's broken and you don't know it yet.

What things you should know when using an Authorize.Net test account. Read on for more info.

If you're confused about what the abbreviations CNP and CP actually mean and wonder why you should even care, read on my friend!

In the final part of this series we make some small changes to make our form ready for live websites and offer a few ideas for how you can improve the form even further. Read more...

Attachments:

payment-form.zip 43 KB

If you haven’t already checked out the Affiliate Reseller program I would suggest you take a few minutes to see what the program has to offer.

Certified Partner Programs have become quite common, find out why the Authorize.Net Certification Program is unique and can add a new lead source to your business.! 

As we near the end of our payment form saga we continue our incremental improvements by refactoring our PHP code to make it easier to maintain. Read more...

Attachments:

payment-form.zip 8 KB

Newcomers and veterans alike, no matter what stage in the development process you’re in, read on to find out where some of the best resources in our Developer Center are located.

In this installment of our series we use HTML and CSS to enhance our form's appearance and increase usability even more.

Attachments:

payment-form.zip 6 KB

Yesterday, Visa released their Best Practices for Mobile Payment Acceptance Practices. Read on to find out more.

We continue to improve upon the payment form we have built in the first seven parts of this series by using JavaScript to increase the usability of our form.

Attachments:

payment-form.zip 8 KB

When you’re designing a payment form or other application, you may find that you need to submit certain fields for your merchant that aren’t specifically supported or called out in our integration guides. Enter the Merchant-Defined Field (MDF)—an easy solution for this common need.

In the first six parts of this series we have built a web form capable of handling online payments and have begun the process of refining and improving it. In Part 7 we continue to improve upon it by learning how to prevent bots from automating form submissions and potentially costing us big bucks.

Attachments:

payment-form.zip 6 KB

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.