Help understanding Authorize.net's AIM

[wavebiddev]

My company builds SaaS tools, and specifically related to Authorize.net, we would like to provide a way for our customers (which are retail companies) to enter an amount and a credit card number and click submit.  Then to have that information together with their login/company configuration go to Authorize.net and charge the consumer's credit card on behalf of the retail company.

From what I'm reading, In order for this to work, each of my customers would need their own API Login ID/Transaction Key.

Am I understanding this correctly?

[RaynorC1emen7]

Yes, each would required open an account with authorize.net

[wavebiddev]

Thank you for your response...Follow up question:  So they would each need their own API Login and Transaction Key....How/Where do they obtain their own, production, login and key?  I've only got the sandbox one, and I'm assuming there is set up somewhere for my customers to connect their Authorize.net Api login with their appropriate merchant account. 

[RaynorC1emen7 · Accepted solution]

Yes, they will have their own loginID and transactionKey

https://www.authorize.net/solutions/merchantsolutions/pricing/