Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →
Access Authorize.Net Data as OData Feeds in Tableau
Use the Tableau Desktop business intelligence tool to connect to Authorize.Net data using the API Server.
The CData API Server, when paired with the ADO.NET Provider for Authorize.Net (or any of 200+ other ADO.NET Providers), provides Authorize.Net data as OData Web services. This article will explain how to use the API Server to provide the underlying connectivity to Authorize.Net data in Tableau's business intelligence tool.
Set Up the API Server
Follow the steps below to begin producing secure Authorize.Net OData services:
Deploy
The API Server runs on your own server. On Windows, you can deploy using the stand-alone server or IIS. On a Java servlet container, drop in the API Server WAR file. See the help documentation for more information and how-tos.
The API Server is also easy to deploy on Microsoft Azure, Amazon EC2, and Heroku.
Connect to Authorize.Net
After you deploy the API Server and the ADO.NET Provider for Authorize.Net, provide authentication values and other connection properties needed to connect to Authorize.Net by clicking Settings -> Connections and adding a new connection in the API Server administration console.
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.
When you configure the connection, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
You can then choose the Authorize.Net entities you want to allow the API Server to access by clicking Settings -> Resources.
Additionally, click Settings -> Server and set the Default Format to XML (Atom) for compatibility with Tableau.
Authorize API Server Users
After determining the OData services you want to produce, authorize users by clicking Settings -> Users. The API Server uses authtoken-based authentication and supports the major authentication schemes. Access can also be restricted based on IP address; by default only connections to the local machine are allowed. You can authenticate as well as encrypt connections with SSL.
Create Real-Time Authorize.Net Data Visualizations
Follow the steps below to create data visualizations based on the remote Authorize.Net data:
-
In Tableau, select 'Connect to data'. In the 'On a server' section, click OData.
-
In the resulting wizard, enter the URL of the OData endpoint for the API Server. Append the name of the table you want to access to the OData entry URL. For example:
https://your-server/api.rsc/SettledBatchList -
Select the
'Use a Username and Password' option and enter the username and password of a user who has access to the API Server.
-
Tableau uses the table metadata exposed by the API Server to detect dimension and measure columns.
-
To view the Authorize.Net data, right-click under the table name in the Data section of the dashboard and select the View Data option. The Authorize.Net data will appear in Tableau.
