Integration and Testing

Authorize.Net API questions and help with your payment integration.

Reply
Member
Posts: 1
Registered: ‎08-13-2011
Accepted Solution

Noob - What API to choose?

My requirement was to use First Data.I tried my best with there API and Web Service but after wasting lots of days couldn't just integrate there API in my application because of Port 1129 and OpenSSL issue as most shared host don't support that. Called them but hardly got any support. First Data don't have any forum or means of communication except call. Tired and decided to use Authorize.Net.

 

I want to process Credit Card for the amount entered by user. I have form with SSL to collect the information. On the server side need to process the transaction with Authorize.Net and show message that payment successfully made.

 

Few things to add:

Credit Card information is not saved on my site

Project is in .NET, C#

Got SSL on shared hosting.

 

Anyone tell what API to use and if there is any sample code?

 

Can we use WebServices for the transaction?

 

Thanks


Accepted Solutions
Solution
Accepted by topic author pirzada
‎08-21-2015 01:58 AM
Posts: 1,609
Topics: 15
Kudos: 209
Solutions: 121
Registered: ‎06-23-2011

Re: Noob - What API to choose?

C# should support all transaction types:

http://developer.authorize.net/downloads/

http://developer.authorize.net/downloads/samplecode/

 

If you're doing one-time charges (as in, the person chooses one or more items, pays for them, and moves on), you want to implement AIM (Advanced Integration Method). This will allow you to charge internally and then display whatever you feel like on success or failure. The users never leave your site. If you're doing more user accounts and ongoing billing (monthly billing, or billing whenever they go over a certain balance) you should implement CIM (Customer Information Manager). ARB (Automated Recurring Billing) also allows for billing at regular intervals, but in my opinion it's a lot more difficult to implement and maintain. Much easier to just run an automated process every morning that identifies charges due and processes them.

 

Short version - AIM or CIM, depending on your needs.

View solution in original post


All Replies
Solution
Accepted by topic author pirzada
‎08-21-2015 01:58 AM
Posts: 1,609
Topics: 15
Kudos: 209
Solutions: 121
Registered: ‎06-23-2011

Re: Noob - What API to choose?

C# should support all transaction types:

http://developer.authorize.net/downloads/

http://developer.authorize.net/downloads/samplecode/

 

If you're doing one-time charges (as in, the person chooses one or more items, pays for them, and moves on), you want to implement AIM (Advanced Integration Method). This will allow you to charge internally and then display whatever you feel like on success or failure. The users never leave your site. If you're doing more user accounts and ongoing billing (monthly billing, or billing whenever they go over a certain balance) you should implement CIM (Customer Information Manager). ARB (Automated Recurring Billing) also allows for billing at regular intervals, but in my opinion it's a lot more difficult to implement and maintain. Much easier to just run an automated process every morning that identifies charges due and processes them.

 

Short version - AIM or CIM, depending on your needs.