The following is a quick overview of the primary classes that are used to accept credit cards from any .NET language. For much more detailed, check out MSDN-style documentation

Classes

There are 3 classes that you will use often:

MinimumCreditCard and Transaction each come in 2 flavors: Standard and Fluent. While you could use both flavors interchangably, it is best just to pick which syntax you prefer and stick with that.

MinimumCreditCard simply exposes a very small subset of the the properties that are available on Transaction. I recommend using MinimumCreditCard all the time and only accessing the additional properties if you need to:

MinimumCreditCard authNet = new MinimumCreditCard()
authNet.Login ("testdrive")
authNet.TranKey("TRANSACTION_KEY")
authNet.Type(TranType.AUTH_CAPTURE)
authNet.CardNum(_cardNumField.Text)
authNet.ExpDate(_cardExpField.Text)
authNet.CardCode(_cardCodeField.Text)
authNet.Amount(8.00);

authNet.Transaction.DriversLicenseNumber("1234567890")
authNet.Transaction.DriversLicenseState("NY")
authNet.Transaction.DriversLicenseDOB("5/5/1972");

if (authNet.Authorize())
{
    // Money in your pocket!
    SaveSuccess(authNet.Response);
}
else
{
	SaveFailure(authNet.Response);
}
	
                        

MinimumCreditCard class

Properties

Methods

Authorize - Sends the transaction to the Authorize.NET Gateway

Above, you already have one example of using the MinimumCreditCard class, so let's skip to the Response class and see how you might use it. Notice that above, we are calling the SaveResults method. Let's go ahead and implement that.

private void SaveSuccess(Response response)
{
	ShoppingCart cart = GetCurrentCart();
	cart.TransactionId = response.TransactionId;
	cart.ApprovalCode = response.ApprovalCode;
	cart.Save();
}

Response class

New Properties

These are the new values that are generated and/or returned by the Authorize.NET gateway.

The different response cores are useful. It is generally recommended that you show the ReasonText to the user in case of failure. It should give them a reasonable idea of what might have gone wrong.

There is a new requirement that if you accept debit or prepaid cards, you must display the amount remaining on the card on the reciept. The BalanceOnCard property allows you to do that. Echoed Properties

These are the values that were passed to the Authorize.NET gateway, in case you didn't keep around that ones that you need.

If you have any questions or doubts then feel free to contact us. We will do our best to help you out.