topic Re: Recurring Billing using AIM in Integration and Testing

Recurring Billing using AIM

su_smart — Fri, 22 Apr 2016 06:41:57 GMT

Hi I am doing payment transaction using AIM,using below code:
Dim post_values As New Dictionary(Of String, String)()

post_values.Add("x_login", ApiLogin)
post_values.Add("x_tran_key", TransactionKey)
post_values.Add("x_delim_data", "TRUE")
post_values.Add("x_delim_char", "|")
post_values.Add("x_relay_response", "FALSE")
post_values.Add("x_type", "AUTH_CAPTURE")
post_values.Add("x_method", "CC")
post_values.Add("x_card_num", txtCardno.Text)
post_values.Add("x_card_code", txtcvv.Text)
post_values.Add("x_exp_date", ddlMonth.SelectedValue + "" + ddlYear.SelectedValue)
post_values.Add("x_amount", "0.1")
post_values.Add("x_description", "")
post_values.Add("x_first_name", "NAMEE")
post_values.Add("x_last_name", "LNAME")
Dim post_string As [String] = ""
For Each post_value As KeyValuePair(Of String, String) In post_values
post_string += post_value.Key + "=" + HttpUtility.UrlEncode(post_value.Value) + "&"
Next
post_string = post_string.TrimEnd("&"c)

'Create an HttpWebRequest object to communicate with Authorize.net
Dim objRequest As HttpWebRequest = DirectCast(WebRequest.Create(post_url), HttpWebRequest)
objRequest.Method = "POST"
objRequest.ContentLength = post_string.Length
objRequest.ContentType = post_url

'post data is sent as a stream
Dim myWriter As StreamWriter = Nothing
myWriter = New StreamWriter(objRequest.GetRequestStream())
myWriter.Write(post_string)
myWriter.Close()

Now I am looking recuuring billing implementation on this code,Please help how I can do that? Help me asap.

Re: Recurring Billing using AIM

RichardH — Fri, 22 Apr 2016 15:53:26 GMT

Hello @su_smart

I suggest starting with our API Reference and look under Recurring Billing.

Richard

Re: Recurring Billing using AIM

Lilith — Fri, 22 Apr 2016 19:29:52 GMT

To expand on @RichardH's comment:

@su_smart is using our legacy AIM API, which does not include integration with our Automated Recurring Billing (ARB) product.

When we created an API for ARB, it became the basis for the current Authorize.Net API, which supercedes the legacy AIM API.

In general we recommend using the full Authorize.Net API over legacy AIM. That would give you support for one-off transactions and ARB, among other features, with one schema and one API endpoint.

Re: Recurring Billing using AIM

su_smart — Mon, 25 Apr 2016 07:34:20 GMT

Hi Thanks for reply,I have few questions:

a> You said the code I am using for AIM is outdated? Is it no more used? Or it just doesn't have feature to integrate Recurring Billing functionality.

b>If my code is old one then please guide me new AIM inetgration code?Is it still called AIM or name has been changed.

c>Also guide me recurring billing code.

Re: Recurring Billing using AIM

Lilith — Mon, 25 Apr 2016 17:00:14 GMT

@su_smart We haven't phased out the Name-Value Pair APIs, including AIM, yet. But AIM was only designed for transaction processing, and has no support for recurring billing.

We're encouraging developers to use the Authorize.Net API, which includes transaction processing (AIM) and recurring billing (ARB) functionality. Please visit https://developer.authorize.net/api/reference/index.html for the documentation.