AuthorizeNot 1.1.4.8

Authorize.Net Python SDK, But It Actually Works.

AuthorizeNot

This package is a fork of the horrifically unmaintained Authorize.Net Python package. Fed up with waiting for the day that never comes, I decided to take things into my own hands. The modifications I have made are simply to get it working on modern versions of Python. There are no new features or functionality compared to the original package. Below are the improvements I have made:

1. The unmaintained PyXB package has been replaced with PyXB-X
2. The massive apicontractsv1.py file has been completely regenerated using the new PyXB-X package and Python 3.12
3. Massive refactoring efforts made with the unittests to get them working with the builtin unittest package instead of the deprecated nosetest package
4. Updated gitignore to prevent many superfluous files from finding their way into your repo
5. Updated the scripts to make regenerating the apicontractsv1.py a little easier

Testing

This project's tests have been updated to simply use the builtin unittest instead of the deprecated nosetest package. Currently, all 15 original unit tests are passing.

Prerequisites

Either:

1. Create a file in the root of the directory named anet_python_sdk_properties.ini
2. Copy the contents of its template file into it
3. Replace the api.login.id and transaction.key variables with your keys

OR

1. Create environment variables api.login.id and transaction.key
2. Set them to your keys

Running The Unit Tests

Simply run python -m unittest. That's it.

Legacy AuthorizeNet README Below

Authorize.Net Python SDK

Requirements

• For Python 2, Python 2.7 or greater
• For Python 3, Python 3.4 or later
• OpenSSL 1.0.2 or greater
• An Authorize.Net account (see Registration & Configuration section below)

Note: Our goal is ensuring this SDK is compatible with Python 2.7+, 3.4+ and PyPy, but at the moment we're primarily testing against Python 2.7.

Contribution

• If you need information or clarification about Authorize.Net features, create an issue with your question. You can also search the Authorize.Net developer community for discussions related to your question.
• Before creating pull requests, please read the contributors guide.

TLS 1.2

The Authorize.Net APIs only support connections using the TLS 1.2 security protocol. Make sure to upgrade all required components to support TLS 1.2. Keep these components up to date to mitigate the risk of new security flaws.

Installation

To install the AuthorizeNet Python SDK:

pip install authorizenet

Registration & Configuration

Use of this SDK and the Authorize.Net APIs requires having an account on the Authorize.Net system. You can find these details in the Settings section. If you don't currently have a production Authorize.Net account, sign up for a sandbox account.

Authentication

To authenticate with the Authorize.Net API, use your account's API Login ID and Transaction Key. If you don't have these credentials, obtain them from the Merchant Interface. For production accounts, the Merchant Interface is located at (https://account.authorize.net/), and for sandbox accounts, at (https://sandbox.authorize.net).

After you have your credentials, load them into the appropriate variables in your code. The below sample code shows how to set the credentials as part of the API request.

To set your API credentials for an API request:

	merchantAuth = apicontractsv1.merchantAuthenticationType()
	merchantAuth.name = 'YOUR_API_LOGIN_ID'
	merchantAuth.transactionKey = 'YOUR_TRANSACTION_KEY'

Never include your API Login ID and Transaction Key directly in a file in a publicly accessible portion of your website. As a best practice, define the API Login ID and Transaction Key in a constants file, and reference those constants in your code.

Switching between the sandbox environment and the production environment

Authorize.Net maintains a complete sandbox environment for testing and development purposes. The sandbox environment is an exact replica of our production environment, with simulated transaction authorization and settlement. By default, this SDK is configured to use the sandbox environment. To switch to the production environment, use the setenvironment method on the controller before executing. For example:

# For PRODUCTION use
	createtransactioncontroller.setenvironment(constants.PRODUCTION)

API credentials are different for each environment, so be sure to switch to the appropriate credentials when switching environments.

Enable Logging in the SDK

Python SDK uses the logger 'authorizenet.sdk'. By default, the logger in the SDK is not configured to write output. You can configure the logger in your code to start seeing logs from the SDK.

A sample logger configuration is given as below:

	import logging
	logger = logging.getLogger('authorizenet.sdk')
	handler = logging.FileHandler('anetSdk.log')  
	formatter = logging.Formatter('%(asctime)s %(name)-12s %(levelname)-8s %(message)s')
	handler.setFormatter(formatter)
	logger.addHandler(handler)
	logger.setLevel(logging.DEBUG)
	logger.debug('Logger set up for Authorizenet Python SDK complete')

SDK Usage Examples and Sample Code

When using this SDK, downloading the Authorize.Net sample code repository is recommended.

• Authorize.Net Python Sample Code Repository (on GitHub)

The repository contains comprehensive sample code for common uses of the Authorize.Net API.

The API Reference contains details and examples of the structure and formatting of the Authorize.Net API.

• Developer Center API Reference

Use the examples in the API Reference to determine which methods and information to include in an API request using this SDK.

Create a Chase Pay Transaction

Use this method to authorize and capture a payment using a tokenized credit card number issued by Chase Pay. Chase Pay transactions are only available to merchants using the Paymentech processor.

The following information is required in the request:

• The payment token,
• The expiration date,
• The cryptogram received from the token provider,
• The tokenRequestorName,
• The tokenRequestorId, and
• The tokenRequestorEci.

When using the SDK to submit Chase Pay transactions, consider the following points:

• tokenRequesterName must be populated with ”CHASE_PAY”
• tokenRequestorId must be populated with the Token Requestor ID provided by Chase Pay services for each transaction during consumer checkout
• tokenRequesterEci must be populated with the ECI Indicator provided by Chase Pay services for each transaction during consumer checkout

Building & Testing the SDK

Requirements

• python 2.7
• pyxb 1.2.5

Run the following to get pyxb and nosetests:

• pip install pyxb==1.2.5
• pip install nose
• pip install lxml

Running the SDK Tests

• Tests available are: unit tests, mock tests, sample code
• use nosetests to run all unittests

>nosetests

Testing Guide

For additional help in testing your own code, Authorize.Net maintains a comprehensive testing guide that includes test credit card numbers to use and special triggers to generate certain responses from the sandbox environment.

Transaction Hash Upgrade

Authorize.Net is phasing out the MD5 based transHash element in favor of the SHA-512 based transHashSHA2. The setting in the Merchant Interface which controlled the MD5 Hash option is no longer available, and the transHash element will stop returning values at a later date to be determined. For information on how to use transHashSHA2, see the [Transaction Hash Upgrade Guide] (https://developer.authorize.net/support/hash_upgrade/).

License

This repository is distributed under a proprietary license. See the provided LICENSE.txt file.