The Authorize.Net Developer Blog

Mobile payments are a growing opportunity for developers. Learn about two new documents from the Payment Card Industry Security Standards Council (PCI SSC) designed to help developers and merchants better understand mobile acceptance security.

This document is an excellent resource for any developer engaged in an e-commerce project involving card payments. 

Rodger Yonley of Advice Interactive Group writes about recurring billing options from Authorize.Net.

Is the increase in mobile devices becoming an opportunity for developers?

Learn how a network breach could potentially expand into payment card processing environments.  Article originally published by Ingrid Beierly of Visa’s Cyber-Security and Investigations team in the Fall 2012 issue of Hospitality Upgrade.

New field added to the CIM hosted form called hostedProfileValidationMode.

Scott Copeland, a technical writer for Authorize.Net, has some questions for community members on how we can improve our documentation.

In order for PrestaShop’s free Authorize.Net module to be successful, developers had to utilize the Advanced Integration Method (AIM). AIM is best described as a customizable payment processing solution that gives merchants control over all steps in processing transactions online.

Just because your business isn't located in the U.S. doesn't mean you can't be part of the Authorize.Net Affiliate Reseller program.

Are you going to the show this week? If so, be sure to stop by our booth!

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.

This weekend the US will be switching to Daylight Savings Time. While this should have little impact, some merchants using SIM or DPM may experience errors related to their transaction fingerprint (RRCs 97, 98, 99 or 103.)

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