Solution ID Implementation Guide

 

Overview

Solution ID enables software vendors to uniquely track the transactions submitted from their application to Authorize.Net.

Unlike your merchant referrals, which are tied only to your Affiliate ID, Solution ID identifies the application creating a transaction for every merchant using your software regardless of who sold the application, gateway or merchant account.  

Partners can create and manage Solution ID within the Partner Interface, and include it in transaction request API calls.

 

Benefits of Solution ID

  • Partners can track every transaction originating from their platform
  • Track software versions through Solution ID setup
  • Partners gain these additional data insights:
    • Total number of merchants using the platform, and aggregated stats related to them
    • Detailed merchant stats for the self-referred merchants to identify top merchants
    • Total number of transactions from each platform and software versions
    • Total payment volume
    • Total refund volume
    • Identify above stats by payment types (ex: CC, ACH)
  • Simplified Customer Service and Gateway error diagnosis due to unique identification of partner transactions

 

Implementation of Solution ID

Important Note: Now Partners can setup multiple Solution IDs that represent their platforms/products/software versions.

Step 1: Create Solution ID

  • Log with your credentials into the Partner Interface
  • Click on Account tab from the top; click Partner Account and expand Solution ID
  • Click on Add Solution ID button
  • Which takes you to this screen
  • Enter values for the fields as described below
    • SOLUTION NAME: Enter your product or application submitting transactions to Authorize.Net
    • VENDOR NAME:  Enter your company name or brand
    • VERSION: Software version.
    • SOLUTION TYPE: Type of software solution such as stand-alone or extension such as plug-in or add-on module
    • PLATFORM: Name of the underlying platform or product used if Solution is an extension.
  • Click on GENERATE ID, review and confirm completing the Solution ID creation
  • Upon Continue, Solution ID is created and displayed in the list view as below

Step 2: Update your Code for createTransactionRequest

  • Update your code for payment transactions using the createTransactionRequest method to include the Solution ID generated in Step 1

Sample name/value pair request snippet:

…

x_solution_id=AAA100302

…

Sample XML request snippet:

...
</payment>
     <solution>
          <id>AAA100302</id>
     </solution>
<order>
...

Step 3: Validate Solution ID Transactions

   <solution>
      <id>
        AAA100302
      </id>
      <name>
        Test Solution #1
      </name>
      <vendor>
        Authorize.Net
      </vendor>
    </solution>
  • Note: Invalid Solution IDs will cause transaction rejections with the following details in the response:
    • Response Code = 265
    • Reason Text= This transaction cannot be accepted
  • Production Solution IDs cannot be used in the sandbox and vice versa
  • If you are testing on your Sandbox, use one of these three Solution IDs that are only applicable to in the sandbox environment: AAA100302, AAA100303, and AAA100304

 

Reports Access

Currently the Authorize.Net Affiliate Team exclusively sends reports until Partner Interface reports are in place:

  • Total number of merchants using the platform, and aggregated stats related to them
  • Merchant level performance stats for the ones referred by you
  • Total number of transactions from each platform and software versions
  • Total payment volume
  • Total refund volume
  • Identify above stats by payment types (ex: CC, ACH)

Help

If you need assistance with implementing Solution ID, please use the contact us form.

References