Ready to get started?

Learn more about the CData ADO.NET Provider for Authorize.Net or download a free trial:

Download Now

Build MVC Applications with Connectivity to Authorize.Net Data

This article shows how to use only the Entity Framework and the CData ADO.NET provider to access Authorize.Net from an ASP.NET MVC application.

This article shows how to use wizards in Visual Studio to drop the CData ADO.NET Provider for Authorize.Net into a simple MVC (model, view, controller) project.

Create the Entity Framework Model

Follow the steps below to save connection properties and map tables to entities in the data model.

  1. Create a new MVC project in Visual Studio. In this example, the project name is MvcAuthorizeNetApp.
  2. If you are using Entity Framework 6, you will need to take the preliminary step of registering the Authorize.Net Entity Framework provider for your project. See the "LINQ and Entity Framework" chapter in the help documentation for a guide.

    Note that MVC 3 scaffolding and MVC 4 scaffolding do not support Entity Framework 6. You can use your scaffolding with Entity Framework 6 by upgrading to the latest version of MVC.

  3. To add the .edmx file from the designer, right-click your Models folder and click Add New Item. Select ADO.NET Entity Data Model, name the model, and click Add. In this example, the name of the model is AuthorizeNetModel.
  4. In the Entity Data Model wizard, select the option 'EF Designer from database'. The Entity Data Model wizard is displayed.
  5. Click New Connection. Select CData Authorize.Net Data Source in the dialog that is displayed.
  6. Specify the required connection string properties.

    You can obtain the necessary connection properties on the Security Settings -> General Settings page after logging into your Merchant Account.

    • UseSandbox: The Authorize.Net API to be used to process transactions. If you are using a production account, this property can be left blank. If you are using a developer test account, set this to 'TRUE'.
    • LoginID: The API login Id associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions. Note that this value is not the same as the login Id that you use to log in to the Merchant Interface.
    • TransactionKey: The transaction key associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions.

    A typical connection string is below:

    LoginId=MyLoginId;TransactionKey=MyTransactionKey;
  7. Name the connection and select whether to include sensitive information, such as connection credentials, in the connection string. For simplicity, this example saves sensitive information in Web.config. The connection settings are saved as AuthorizeNetEntities.

  8. Select the views you need. In this example, SettledBatchList is imported. Also, the option to pluralize object names is deselected in this example. Click Finish to create the .edmx file.
  9. Build your project to complete this step.

Scaffold the Controller and Views

After creating the model and building the project, you can use ASP.NET Scaffolding wizards to create the controller and the views.

  1. In Solution Explorer, right-click the controllers folder and click Add -> Controller. Select MVC 5 Controller with views, using Entity Framework.
  2. In the Add Controller dialog that is then displayed, select the following options:

    • Model class: Select a table you imported; for example, SettledBatchList.
    • Data context class: Select your context class.
  3. Leave the default values for the other fields.

You can now access the list of SettledBatchList records at http://MySite/SettledBatchList. With every state change the site picks up any data changes.