Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Authorize.Net CIM gateway #51

Closed
wants to merge 10 commits into from

Conversation

pilot
Copy link
Contributor

@pilot pilot commented Apr 24, 2013

No description provided.

@pilot
Copy link
Contributor Author

pilot commented Apr 24, 2013

@adrianmacneil it's will be good if you create a new tag after merge, I'll add a changelog file after tagging

@amacneil
Copy link
Member

Does this need to be a separate gateway? Can't you just add createCard/updateCard/deleteCard methods to the AIMGateway?

@pilot
Copy link
Contributor Author

pilot commented Apr 26, 2013

It should be separeated cause it's standalone gate in Authorize, called CIM. Only CIM support saving card and Authorize take additional fee.

@amacneil
Copy link
Member

Yeah, but you use it in conjunction with AIM and SIM right, with the same credentials? If you configured a shopping cart with AIM and also wanted it to optionally store cards, you would use the same API credentials. Just the same as with Stripe when you store a card for token billing.

@pilot
Copy link
Contributor Author

pilot commented Apr 26, 2013

There is is a two case, right and not right, if you use a AIM teoretical you can CRUD card/profile, and it's a no problem, But you can't bill on surch card cause authorize/purchase etc. request is different then for AIM or SIM.

So for do it right you should switch from AIM or SIM to CIM, or handle both, AIM or SIM for direct capture, and CIM for capture saved customer credit cards

@pilot
Copy link
Contributor Author

pilot commented Apr 26, 2013

I'm no see a sense to copy all calls from CIMGateway to the AIM or SIM cause we should copy tottaly all calls

@pilot
Copy link
Contributor Author

pilot commented Apr 26, 2013

But seems we can add a call CIM CRUD or Capture from AIM or SIM without additional gate configuration, just as additional options, but stay CIM standalone casue for it usign no need AIM or SIM

@amacneil
Copy link
Member

Ok I just looked into this more. We need to update the AIM gateway to use the new XML API, and at the same time integrate CIM, so that if the developer sends calls authorize() with card Omnipay calls AIM and if they use cardReference Omnipay calls CIM (they have the same endpoint anyway).

CIM shouldn't be a separate gateway, because it is essentially a fancy name for the token billing parts of Authorize.net. Omnipay's design goal is to abstract the differences between gateways, so the classes should be structured around our own API and not Authorize.net's bizarre product lineup.

The developer using Omnipay does care that CIM is a separate product/addon. They should be able to just do:

$gateway->authorize(array('card' => array()));
// OR
$gateway->authorize(array('cardReference' => 'abc'))

The requirement is that this can be used in a shopping cart which can use generic calls on every gateway and not need to know the differences between each gateway.

@pilot
Copy link
Contributor Author

pilot commented Apr 29, 2013

Ok, get your point, will update AIM with CIM integration

@cfreear
Copy link
Contributor

cfreear commented May 2, 2013

@pilot are you currently looking at switching AIM to XML? I was looking to implement credit/refunds in AIM but I'll hold out on doing it if you are currently working on the gateway.

@pilot
Copy link
Contributor Author

pilot commented May 2, 2013

Yep currently on switching AIM to use xml, plan to implement during a week

Cheers
Alex

On Thu, May 2, 2013 at 10:47 AM, Christian Freear
[email protected] wrote:

@pilot are you currently looking at switching AIM to XML? I was looking to implement credit/refunds in AIM but I'll hold out on doing it if you are currently working on the gateway.

Reply to this email directly or view it on GitHub:
#51 (comment)

@amacneil amacneil closed this Jun 2, 2013
@mathewpeterson
Copy link

Did this move any further?

@pilot
Copy link
Contributor Author

pilot commented Oct 29, 2013

@mathewpeterson I hope to refactor it in near feature

@rushi
Copy link

rushi commented Aug 3, 2014

@pilot @adrianmacneil There is a new PR for switching the AIM gateway to the XML API thephpleague/omnipay-authorizenet#6

@rushi
Copy link

rushi commented Nov 27, 2014

The CIM Gateway is now supported on xola/authorizenet and there's a PR for it too thephpleague/omnipay-authorizenet#6

barryvdh pushed a commit that referenced this pull request Feb 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants