Ready to get started?

Learn more or sign up for a free trial:

CData Connect Server

Search External Authorize.Net Objects in Salesforce Connect



Use CData Connect Server to securely provide OData feeds of Authorize.Net data to smart devices and cloud-based applications. Use the CData Connect and Salesforce Connect to create Authorize.Net objects that you can access from apps and the dashboard.

CData Connect Server, enables you to access Authorize.Net data from cloud-based applications like the Salesforce console and mobile applications like the Salesforce1 Mobile App. In this article, you will use CData Connect Server and Salesforce Connect to access external Authorize.Net objects alongside standard Salesforce objects.

Configuring Connect Server

To work with live Authorize.Net data in Salesforce Connect, we need to connect to Authorize.Net from Connect Server, provide user access to the new virtual database, and create OData endpoints for the Authorize.Net data.

Add a Connect Server User

Create a User to connect to Authorize.Net from Reveal through Connect Server.

  1. Click Users -> Add
  2. Configure a User
  3. Click Save Changes and make note of the Authtoken for the new user

Connect to Authorize.Net from Connect Server

CData Connect Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.

  1. Open Connect Server and click Connections
  2. Select "Authorize.Net" from Available Data Sources
  3. Enter the necessary authentication properties to connect to Authorize.Net.

    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.
  4. Click Save Changes
  5. Click Privileges -> Add and add the new user (or an existing user) with the appropriate permissions (SELECT is all that is required for Reveal).

Add Authorize.Net OData Endpoints in Connect Server

After connecting to Authorize.Net, create OData Endpoints for the desired table(s).

  1. Click OData -> Tables -> Add Tables
  2. Select the Authorize.Net database
  3. Select the table(s) you wish to work with and click Next
  4. (Optional) Edit the table definition to select specific fields and more
  5. Save the settings

(Optional) Configure Cross-Origin Resource Sharing (CORS)

When accessing and connecting to multiple different domains, there is a possibility of violating the limitations of cross-site scripting. In that case, configure the CORS settings in OData -> Settings.

  • Enable cross-origin resource sharing (CORS): ON
  • Allow all domains without '*': ON
  • Access-Control-Allow-Methods: GET, PUT, POST, OPTIONS
  • Access-Control-Allow-Headers: Authorization

Save the changes to the settings.

Connect to Authorize.Net Data as an External Data Source

Follow the steps below to connect to the feed produced by the API Server.

  1. Log into Salesforce and click Setup -> Integrations -> External Data Sources.
  2. Click New External Data Source.
  3. Enter values for the following properties:
    • External Data Source: Enter a label to be used in list views and reports.
    • Name: Enter a unique identifier.
    • Type: Select the option "Salesforce Connect: OData 4.0".
    • URL: Enter the URL to the OData endpoint of the API Server. The format of the OData URL is CONNECT_SERVER_URL/api.rsc/

  4. Select JSON in the Format menu.

  5. In the Authentication section, set the following properties:
    • Identity Type: If all members of your organization will use the same credentials to access the API Server, select "Named Principal". If the members of your organization will connect with their own credentials, select "Per User".
    • Authentication Protocol: Select Password Authentication to use basic authentication.
    • Certificate: Enter or browse to the certificate to be used to encrypt and authenticate communications from Salesforce to your server.
    • Username: Enter the username for a user known to CData Connect Server.
    • Password: Enter the user's authtoken.

Synchronize Authorize.Net Objects

After you have created the external data source, follow the steps below to create Authorize.Net external objects that reflect any changes in the data source. You will synchronize the definitions for the Authorize.Net external objects with the definitions for Authorize.Net tables.

  1. Click the link for the external data source you created.
  2. Click Validate and Sync.
  3. Select the Authorize.Net tables you want to work with as external objects.

Access Authorize.Net Data as Salesforce Objects

After adding Authorize.Net data as an external data source and syncing Authorize.Net tables as external objects, you can use the external Authorize.Net objects just as you would standard Salesforce objects.

  • Create a new tab with a filter list view:

  • Create reports of external objects:

Simplified Access to Authorize.Net Data from Applications

At this point, you have a direct connection to live Authorize.Net data from Salesforce. For more information on gaining simplified access to data from more than 100 SaaS, Big Data, and NoSQL sources in applications like Salesforce, refer to our Connect Server page.