Add virtualenv folder to ignore list
Remove test status from form

Authorize.net automatically dumps any transactions that have a test mode
of true. This is so you can test the functionality in production without
test transactions polluting your history.

However, it also dumps test transactions in the test environment, so
these will not show up in your sandbox transaction history.
Be consistent with quoting and case
Make sure scheme is in the domain

For the relay system to work you must explicitly set the scheme for the
URL. Authorize.net does not assume HTTP or HTTPS (at least that has
been my experience in testing).

Also, authorize.net will only send on ports 80 and 443.
Fix missing currency code

If you include the currency code in the Fingerprint you MUST include the
currency code in the POST request to the transaction gateway, or the
fingerprints will fail.

Notice that when using the Fingerprint tool
https://developer.authorize.net/tools/responsecode99/?page_id=7199
It will ask you for the currency code. The currency code is 3 characters
so make sure you are sending the correct currency code. The tool or
service does not issue an error.

That is if you use US instead of USD, your fingerprints will fail and
you will have no idea why. Same if you include the currency code in your
fingerprint and not int he PSOT request, the fingerprint will fail.
Remove currency code

There are apparently some issues with this. According to the
documentation, if you include a currency code in the hash, you need to
include the x_currency_code field in the form, however, no transactions
will go through with this.

We will just let it default to the merchant configured currency in the
settings of the authorize.net account.